Here is an example for creating a simple java RSS reader and setting flume up to read the output: http://www.ibm.com/developerworks/library/bd-flumews/ -pd ... View more

Thats definitely unusual, the sentry.service.allow.connect governs access and would throw that exception you are observing. Can you confirm that you do have the kafka system user as 'kafka' and that there aren't any typos? Can you include the sentry stack trace with the exception? Additionally, can you run the following, both on the kafka broker and sentry node and confirm they match: id kafka -pd ... View more

You could have an issue with certificates...if you enable DEBUG for the client, you should be able to determine what it's having issues with: cp /etc/kafka/conf/tools-log4j.properties /var/tmp sed -i -e 's/INFO/DEBUG/g' /var/tmp/tools-log4j.properties export KAFKA_OPTS="-Dlog4j.configuration=file:/var/tmp/tools-log4j.properties -Djava.security.auth.login.config=/path/to/jaas.conf" -pd ... View more

meta.properties was likely left over from a previous instance of the kafka broker. Did you remove the broker role instances and recreate them on the same machine? When that happens, the broker.id changes and kafka won't start properly as a safety measure. A good rule of thumb is if you need to remove the role instances and recreate, then delete everything from the kafka data dir (unless you need to use the partitions), in which case, you'll have to update that meta.properties file manually. -pd ... View more

This appears to be your problem: 17/03/26 19:26:24 INFO utils.VerifiableProperties: Property metadata.broker.list is overridden to 0.0.0.0:9092 Are you setting metadata.broker.list in your kafka.properties on the brokers? What is your LISTENERS property set to on the brokers? -pd ... View more