nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "West, Joshua" <>
Subject Re: Nifi 0.50 and GetKafka Issues
Date Sun, 21 Feb 2016 21:28:49 GMT
Hi Oleg,

Ahh.  That's a shame.  Hopefully the maintainers post this note in the release notes or documentation
as I'm sure others will run into problems when upgrading Nifi while using existin kafka 0.8.x

We look like we'll end up sticking with Kafka and Nifi 0.4.1 for a while as we also
make use of Apache Storm, which only supports the Kafka 0.8.x series.

Thanks for clarifying things.

Josh West <>
Bose Corporation

On Sat, 2016-02-20 at 23:47 +0000, Oleg Zhurakousky wrote:

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