Re: Reg : Unable to produce message

Sorry I miss to mention the topics which I was trying are already existing and worked before. When I try to list topics and try to get topic information I was able to get all the details including leader selected. But if I try to produce I am getting this problem. And this happened to few topics an

What happens if controlled shutdown can't complete within controlled.shutdown.max.retries attempts?

The broker has the following parameters related to controlled shutdown: controlled.shutdown.enable Enable controlled shutdown of the server boolean truemedium controlled.shutdown.max.retries Controlled shutdown can fail for multiple reasons. This determines the number of

Help understanding what happened

In a test in staging environment, we kill -9 the broker. It was started back up by runit and started recovering. We are seeing errors like this: WARN Found an corrupted index file, /mnt/services/kafka/data/TOPIC-17/16763460.index, deleting and rebuilding index... (kafka.log.Log) The f

RE: Reg : Unable to produce message

Hi Ashiq, I am going through the same trouble with 0.9.0.0 and 0.9.0.1 for entirely new installation on remote VM. But from search across mailing lists and other sources, many seem to have had success when they have set the advertised.host.name with proper broker host name and using the same

Re: Larger Size Error Message

Hi Guozhang, The problem is that server "10.225.36.226" is not one of my kafka clients, nslookup shows it is another internal server, my servers are like 10.224.146.6 #, I can't even login to that server. All of my messages are at most a few KB. Is it possible anybody

Consumer 0.9 /Broker 0.9.0.1 - for certain partitions, the commit offset in kafka alway gets rewinded to a fixed point

I am seeing a very wired issue with my consumer group when running consumer 0.9 with broker 0.9.0.1. On adding or removing consumers, it seems that for certain partitions the commit offset in kafka alway gets rewinded to a fixed point. When I run the below command over time to look at my consumer

Re: Consumer 0.9 /Broker 0.9.0.1 - for certain partitions, the commit offset in kafka alway gets rewinded to a fixed point

Hi Saurabh, When you say Consumer 0.9, do you mean 0.9.0.0? If so, you should really upgrade to 0.9.0.1 as it contains a number of important fixes. Ismael On Sun, Mar 20, 2016 at 6:31 PM, Saurabh Daftary wrote: > I am seeing a very wired issue with my consumer group when running consumer > 0.9

Re: Consumer 0.9 /Broker 0.9.0.1 - for certain partitions, the commit offset in kafka alway gets rewinded to a fixed point

Yes, I do mean 0.9.0.0. I am planning to upgrade to 0.9.0.1 but was wondering if this was a known issue in 0.9.0.0 On Sun, Mar 20, 2016 at 11:31 AM, Saurabh Daftary wrote: > I am seeing a very wired issue with my consumer group when running > consumer 0.9 with broker 0.9.0.1. On adding or removi

Re: Consumer 0.9 /Broker 0.9.0.1 - for certain partitions, the commit offset in kafka alway gets rewinded to a fixed point

See here for important issues fixed in 0.9.0.1: http://www.confluent.io/blog/announcing-apache-kafka-0.9.0.1-and-confluent-platform-2.0.1 Upgrading is highly recommended. Ismael On Sun, Mar 20, 2016 at 11:20 PM, Saurabh Daftary wrote: > Yes, I do mean 0.9.0.0. I am planning to upgrade to 0.9.

Re: For SSL config, Any way to avoid the cleartext passwords?

One option is that your application could read the password from an access restricted file (e.g. owner read/write only) or retrieve it from a credentials server (e.g. hadoop kms, hashicorp vault) For what its worth, java keystore passwords are pretty useless anyway and keystores can be read withou

two questions

1) I am using the upgrade instructions to upgrade from 0.8 to 0.9. Can someone tell me if i need to continue to bump the inter.broker.protocol.version after each upgrade? Currently the broker code is 0.9.0.1 but i have the config file listing as inter.broker.protocol.versi on=0.9.0.0 2) Is it possi

Would Kafka streams be a good choice for a collaborative web app?

Hi, I'm soon to begin design and dev of a collaborative web app where changes made by one user should appear to other users in near real time. I'm new to Kafka, but having read a bit about Kafka streams I'm wondering if it would be a good solution. Change events produced by one user would be