I just commented, it will be fixed as part of https://issues.apache.org/jira/browse/NIFI-1684
Cheers Oleg On Mar 25, 2016, at 4:31 PM, Oleg Zhurakousky <[email protected]<mailto:[email protected]>> wrote: It is a problem with Random, it's bootstrapping the wrong class and that is the bug Sent from my iPhone On Mar 25, 2016, at 16:27, McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote) <[email protected]<mailto:[email protected]>> wrote: I’m still playing with it and I’m not sure exactly what is going on. I think though, there is a problem with the Random partitioning strategy, but I am not sure yet. Another small problem I am seeing is this. 2016-03-25 20:15:25,637 ERROR [Timer-Driven Process Thread-3] o.a.nifi.processors.kafka.KafkaPublisher Failed while waiting for acks from Kafka java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.RecordTooLargeException: The message is 2163182 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration. The problem isn’t the error per-se. Yes, my message is too big. The problem is that the bulletin for this is "Failed while waiting for acks from Kafka” which is misleading. I’m pretty sure this is a regression. I can file a Jira for this, if you like. On 3/25/16, 4:11 PM, "Oleg Zhurakousky" <[email protected]<mailto:[email protected]>> wrote: The spell checker got the best of me here, I meant to say ‘surgery’ instead of ‘survey’. Oleg On Mar 25, 2016, at 3:50 PM, Oleg Zhurakousky <[email protected]<mailto:[email protected]>> wrote: Chris Indeed PutKafka had some significant survey lately. But what you see is actually a bug. Would you mind raising JIRA? Thanks Oleg On Mar 25, 2016, at 3:42 PM, McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote) <[email protected]<mailto:[email protected]>> wrote: I work around the problem by stopping the PutKafka processor, changing its partitioning strategy from Random to RoundRobin. Afterwards, I stopped it and changed it back, and it continued worked fine. The flow I had was from an older version of NiFi. I’m guessing its some sort of upgrade issue? On 3/25/16, 2:47 PM, "McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote)" <[email protected]<mailto:[email protected]>> wrote: I’m running the latest from master which I built myself. I’m encountering the follow PutKafka error. Any suggestions? Caused by: java.lang.IllegalStateException: Failed to create partitioner at org.apache.nifi.processors.kafka.KafkaPublisher.<init>(KafkaPublisher.java:75) ~[na:na] at org.apache.nifi.processors.kafka.PutKafka.createKafkaPublisher(PutKafka.java:282) ~[na:na] ... 14 common frames omitted Caused by: java.lang.InstantiationException: kafka.producer.DefaultPartitioner at java.lang.Class.newInstance(Class.java:427) ~[na:1.8.0_45] at org.apache.nifi.processors.kafka.KafkaPublisher.<init>(KafkaPublisher.java:70) ~[na:na] ... 15 common frames omitted Caused by: java.lang.NoSuchMethodException: kafka.producer.DefaultPartitioner.<init>() at java.lang.Class.getConstructor0(Class.java:3082) ~[na:1.8.0_45] at java.lang.Class.newInstance(Class.java:412) ~[na:1.8.0_45] ... 16 common frames omitted Thanks, Chris
