Excuse me my message got cut short. I point you to the state management section since you mention you are using zookeeper and you are running nifi in cluster mode. The default cluster state provider is ZookeeperStateProvider
Thanks On Sat, Feb 20, 2016 at 7:29 PM, Juan Sequeiros <[email protected]> wrote: > Joshua, > > Did you edit the state-management.xml > Take a look at the state management section of the admin guide throuigh > the instances "help" link. > > > On Sat, Feb 20, 2016 at 6:47 PM, Oleg Zhurakousky < > [email protected]> wrote: > >> Josh >> >> 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. >> >> Oleg >> >> On Feb 20, 2016, at 4:10 PM, West, Joshua <[email protected]> wrote: >> >> Hi Oleg and Joe, >> >> Kafka 0.8.2.1 >> >> Attached is the app log with hostnames scrubbed. >> >> Thanks for your help. Much appreciated. >> >> -- >> Josh West <[email protected]> >> 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" <[email protected]> >> wrote: >> >> Josh >> >> Any chance to attache the app-log or relevant stack trace? >> >> Thanks >> Oleg >> >> On Feb 20, 2016, at 3:30 PM, West, Joshua <[email protected]> wrote: >> >> 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. >> 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: >> >> zookeeper-node1:2181,zookeeper-node2:2181,zookeeper-node3:2181/kafka >> >> Is anybody else experiencing issues? >> >> Thanks. >> >> -- >> Josh West <[email protected]> >> >> Cloud Architect >> Bose Corporation >> >> >> >> >> >> <nifi-app.log.kafkaissues.bz2> >> >> >> > > > -- > Juan Carlos Sequeiros > -- Juan Carlos Sequeiros
