Re: Kafka consumers unable to process message

dnesday, August 31, 2016 10:56 PM > To: us...@kafka.apache.org > Cc: dev@kafka.apache.org > Subject: Re: Kafka consumers unable to process message > > The exceptions show one of the replica fetcher threads on the broker > failing which makes perfect sense since some of the partitions we

RE: Kafka consumers unable to process message

for your response. -Original Message- From: Jason Gustafson [mailto:ja...@confluent.io] Sent: Wednesday, August 31, 2016 10:56 PM To: us...@kafka.apache.org Cc: dev@kafka.apache.org Subject: Re: Kafka consumers unable to process message The exceptions show one of the replica fetcher threads

Re: Kafka consumers unable to process message

6] INFO [Group Metadata Manager on Broker 4]: > Removed 0 expired offsets in 1 milliseconds. (kafka.coordinator. > GroupMetadataManager) > [2016-09-01 02:33:04,926] INFO [Group Metadata Manager on Broker 4]: > Removed 0 expired offsets in 1 milliseconds. (kafka.coordinator. > GroupMet

RE: Kafka consumers unable to process message

: Jason Gustafson [mailto:ja...@confluent.io] Sent: Wednesday, August 31, 2016 10:26 PM To: us...@kafka.apache.org Cc: dev@kafka.apache.org Subject: Re: Kafka consumers unable to process message Hi Achintya, Just to clarify, you did not take down either of the zookeepers in this test, right

Re: Kafka consumers unable to process message

uot;org.apache.kafka.common. > serialization.StringDeserializer"); > props.put("value.deserializer", > "com.comcast.ps.kafka.object.CustomMessageDeSer"); > > Is it because of consumer is not able to get the broker metadata if it is > trying to connect oth

RE: Kafka consumers unable to process message

;value.deserializer", "com.comcast.ps.kafka.object.CustomMessageDeSer"); Is it because of consumer is not able to get the broker metadata if it is trying to connect other datacenter's zookeeper server? I tried with to increate the zookeeper session timeout and connection time out but no l

Re: Kafka consumers unable to process message

Kafka clients have tended to make broker retries transparent to the user. There's been discussion on various JIRAs about what we should do when all the known brokers become unreachable. One option is to revert to the configured bootstrap broker list, which is nice if you've configured a vip for

Re: Kafka consumers unable to process message

Yeah, let's figure out the "best" action to take... Looks like something I'd like to get a handle on. > On Aug 31, 2016, at 4:05 PM, Jason Gustafson wrote: > > Hi Achintya, > > We have a JIRA for this problem: https://issues. > apache.org/jira/browse/KAFKA-3834. Do you

Re: Kafka consumers unable to process message

Hi Achintya, We have a JIRA for this problem: https://issues. apache.org/jira/browse/KAFKA-3834. Do you expect the client to raise an exception in this case or do you just want to keep it from blocking indefinitely? If the latter, you could escape the poll from another thread using wakeup().