Re: Message loss with kafka 0.8.2.2

Did you check if the controller is active in the cluster? If the controller isn't active (there are known 0.8 bugs that can lead to this), then this could cause this kind of data loss issue. I recommend upgrading to 0.9 ASAP. Thanks Tom Crayford Heroku Kafka On Friday, 17 June 2016, Gulia, Vikra

Re: Message loss with kafka 0.8.2.2

Hi Gerard, thanks for the reply. Few follow ups - 1. I can try setting acks = all but wouldn't it lead to performance hit (I am using sync produce thus response time will be more). 2. I will try unclean.leader.election.enable = false and update you if it helps. 3. Regarding your last point, I am c

Re: Message loss with kafka 0.8.2.2

You could try set the acks to -1, so you wait for the produce to be succesfull, until most other brokers also received the message. Another thing you could try is set the unclean.leader.election.enable to false (this is a setting on the broker). I think what's happening now is that the message in y

Message loss with kafka 0.8.2.2

Hi Users, I am facing message loss while using kafka v 0.8.2.2. Please see details below and help me if you can. Issue: 2 messages produced to same partition one by one – Kafka producer returns same offset back which means message produced earlier is lost.