Hello, we have recently upgraded to 2.11-1.1.0, but for our publish-subscribe design we are still using Producer and Consumer API from 0.10.2.1. We understand there are more enhanced features in new 1.1 API but we aren't using those specific items.
Upon upgrade, we confirmed that some test messages can be exchanged. But with the same configuration as our 0.10.2.1 setup, we see that consumer.poll(2000L) call never returns any data. As a result we have a huge queue of messages pending even though a simple command line consumer is able to get them all. But as soon as we increased the value to 4000L, we received all data. Is this tweaking expected for any such upgrade? Or do we need to move to new Producer/Consumer API? Any suggestion is appreciated. Attached is the broker and consumer files. Regards,
# Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # see kafka.server.KafkaConfig for additional details and defaults ############################# Server Basics ############################# # The id of the broker. This must be set to a unique integer for each broker. broker.id=1 # Switch to enable topic deletion or not, default value is false #delete.topic.enable=true ############################# Socket Server Settings ############################# # The address the socket server listens on. It will get the value returned from # java.net.InetAddress.getCanonicalHostName() if not configured. # FORMAT: # listeners = listener_name://host_name:port # EXAMPLE: # listeners = PLAINTEXT://your.host.name:9092 advertised.listeners=PLAINTEXT://com-domain-kafkamachine-233:9092 #port=9092 #host.name=com-domain-kafkamachine-233 # Hostname and port the broker will advertise to producers and consumers. If not set, # it uses the value for "listeners" if configured. Otherwise, it will use the value # returned from java.net.InetAddress.getCanonicalHostName(). # advertised.listeners=PLAINTEXT://localhost:9092 # Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL #SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL # The number of threads handling network requests num.network.threads=9 # The number of threads doing disk I/O num.io.threads=24 # The send buffer (SO_SNDBUF) used by the socket server socket.send.buffer.bytes=102400 # The receive buffer (SO_RCVBUF) used by the socket server socket.receive.buffer.bytes=102400 # The maximum size of a request that the socket server will accept (protection against OOM) socket.request.max.bytes=999999999 ############################# Log Basics ############################# # A comma seperated list of directories under which to store log files log.dirs=/kafka1 # The default number of log partitions per topic. More partitions allow greater # parallelism for consumption, but this will also result in more files across # the brokers. num.partitions=1 # The number of threads per data directory to be used for log recovery at startup and flushing at shutdown. # This value is recommended to be increased for installations with data dirs located in RAID array. num.recovery.threads.per.data.dir=1 ############################# Log Flush Policy ############################# # Messages are immediately written to the filesystem but by default we only fsync() to sync # the OS cache lazily. The following configurations control the flush of data to disk. # There are a few important trade-offs here: # 1. Durability: Unflushed data may be lost if you are not using replication. # 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush. # 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks. # The settings below allow one to configure the flush policy to flush data after a period of time or # every N messages (or both). This can be done globally and overridden on a per-topic basis. # The number of messages to accept before forcing a flush of data to disk #log.flush.interval.messages=10000 # The maximum amount of time a message can sit in a log before we force a flush #log.flush.interval.ms=1000 ############################# Log Retention Policy ############################# # The following configurations control the disposal of log segments. The policy can # be set to delete segments after a period of time, or after a given size has accumulated. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens # from the end of the log. # The minimum age of a log file to be eligible for deletion due to age log.retention.hours=2 log.retention.minutes=15 # A size-based retention policy for logs. Segments are pruned from the log as long as the remaining # segments don't drop below log.retention.bytes. Functions independently of log.retention.hours. log.retention.bytes=20971520 # The maximum size of a log segment file. When this size is reached a new log segment will be created. log.segment.bytes=10485760 log.roll.hours=1 # The interval at which log segments are checked to see if they can be deleted according # to the retention policies log.retention.check.interval.ms=300000 ## Offset retention policy ## offsets.retention.minutes Retains for no. minutes offsets.retention.minutes=2880 ## offsets.retention.check.interval.ms checks at the specified interval whether any committed offset can be deleted offsets.retention.check.interval.ms=300000 log.cleanup.policy=delete ############################# Zookeeper ############################# # Zookeeper connection string (see zookeeper docs for details). # This is a comma separated host:port pairs, each corresponding to a zk # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002". # You can also append an optional chroot string to the urls to specify the # root directory for all kafka znodes. zookeeper.connect=com-domain-kafkamachine-233:2181,com-domain-kafkamachine-245:2181,com-domain-kafkamachine-219:2181 # Timeout in ms for connecting to zookeeper zookeeper.connection.timeout.ms=35000 zookeeper.session.timeout.ms=20000 # Compression details compression.type=gzip # delete topic enable delete.topic.enable=true # metrics reporter properties kafka.metrics.polling.interval.secs=5 kafka.metrics.reporters=kafka.metrics.KafkaCSVMetricsReporter kafka.csv.metrics.dir=/tmp/kafka_metrics # Disable csv reporting by default. kafka.csv.metrics.reporter.enabled=false #Graceful shutdown enabled by default #backoff is the wait time before every retry controlled.shutdown.max.retries=10 controlled.shutdown.retry.backoff.ms=3000 request.timeout.ms=45000
# Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # see kafka.consumer.ConsumerConfig for more details # Zookeeper connection string # comma separated host:port pairs, each corresponding to a zk # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002" bootstrap.servers=com-domain-kafkamachine-233:9092,com-domain-kafkamachine-245:9092,com-domain-kafkamachine-219:9092 # timeout in ms for connecting to zookeeper #zookeeper.connection.timeout.ms=6000 #consumer group id group.id=fgvms1 enable.auto.commit=false # earliest - For any new group joining, start from the beginning # earliest - For any existing group joining/rejoining - IGNORE this and start from last committed offset # latest - For any new group joining - wait until new data is available. # latest - For any existing group joining - IGNORE this and start from last committed offset auto.offset.reset=earliest fetch.min.bytes=10 max.poll.interval.ms=2147483647 session.timeout.ms=20000 #consumer timeout #consumer.timeout.ms=5000 key.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer value.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer
