nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Zhurakousky <>
Subject Re: Nifi 0.50 and GetKafka Issues
Date Sun, 21 Feb 2016 15:02:50 GMT

Also, keep in mind that there are incompatible property names in Kafka between the 0.7 and
0.8 releases. One of the change that went it was replacing “” with
“”. Not sure if it’s related though, but realizing that
0.4.1 was relying on this property it’s value was completely ignored with 0.8 client libraries
(you could actually see the WARN message to that effect) and now it is not ignored, so take
a look and see if tinkering with its value changes something.

On Feb 20, 2016, at 6:47 PM, Oleg Zhurakousky <<>>


The only change that ’s went and relevant to your issue is the fact that we’ve upgraded
client libraries to Kafka 0.9 and between 0.8 and 0.9 Kafka introduced wire protocol changes
that break compatibility.
I am still digging so stay tuned.


On Feb 20, 2016, at 4:10 PM, West, Joshua <<>>

Hi Oleg and Joe,


Attached is the app log with hostnames scrubbed.

Thanks for your help.  Much appreciated.

Josh West <<>>
Bose Corporation

On Sat, 2016-02-20 at 15:46 -0500, Joe Witt wrote:

And also what version of Kafka are you using?

On Feb 20, 2016 3:37 PM, "Oleg Zhurakousky" <<>>

Any chance to attache the app-log or relevant stack trace?


On Feb 20, 2016, at 3:30 PM, West, Joshua <<>>

Hi folks,

I've upgraded from Nifi 0.4.1 to 0.5.0 and I am no longer able to use the GetKafka processor.
 I'm seeing errors like so:

2016-02-20 20:10:14,953 WARN [ConsumerFetcherThread-NiFi-sldjflkdsjflksjf_**SCRUBBED**-1455999008728-5b8c7108-0-0]
kafka.consumer.ConsumerFetcherThread [ConsumerFetcherThread-NiFi-sldjflkdsjflksjf_**SCRUBBED**-1455999008728-5b8c7108-0-0],
Error in fetchkafka.consumer.ConsumerFetcherThread$FetchRequest@7b49a642<mailto:kafka.consumer.ConsumerFetcherThread$FetchRequest@7b49a642>.
Possible cause: java.lang.IllegalArgumentException

^ Note  the hostname of the server has been scrubbed.

My configuration is pretty generic, except that with Zookeeper we use a different root path,
so our Zookeeper connect string looks like so:


Is anybody else experiencing issues?


Josh West <<>>

Cloud Architect
Bose Corporation


View raw message