----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52403/#review150948 -----------------------------------------------------------
Ship it! lgtm. Thanks! samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemProducer.scala (line 59) <https://reviews.apache.org/r/52403/#comment219050> nit: be consistent w/ the code: exceptionInCallback samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemProducer.scala (line 103) <https://reviews.apache.org/r/52403/#comment219045> So, close() w/ timeout 0 is only available in Kafka 0.9 and above? I think that for 0.11, let's still use Kafka 0.8.2. In 0.12, we should include SAMZA-855 and upgrade to Kafka 0.10. - Yi Pan (Data Infrastructure) On Sept. 29, 2016, 9:23 p.m., Xinyu Liu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/52403/ > ----------------------------------------------------------- > > (Updated Sept. 29, 2016, 9:23 p.m.) > > > Review request for samza, Navina Ramesh and Jagadish Venkatraman. > > > Repository: samza > > > Description > ------- > > Current the error log happens after produce close and reset the exception in > later callbacks, which caused the trouble shooting to be harder in cases of > multithreading. We should log error before closing and keep atomic reference > of the initial exception. > > > Diffs > ----- > > > samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemProducer.scala > 5ff6d3caf54ed148aa40c7c752c587e556a4f34a > > Diff: https://reviews.apache.org/r/52403/diff/ > > > Testing > ------- > > Tested in jobs deployed in Yarn cluster. > > > Thanks, > > Xinyu Liu > >
