Hi Kafka Dev Team, We have to similar change for # 2 issue, I would like to know if /KAFKA-1788 <https://issues.apache.org/jira/browse/KAFKA-1788> will be part of release. Secondly, issue #1, I would like to know what is expected behavior of metrics error counting and call back in (async mode) when there is no issues with ZK or Brokers but network layer (firewalll or DNS issue) only.
If need to be, I can file a jira ticket after understanding behavior and I can test expected behavior as well. Thanks, Bhavesh On Fri, Jan 2, 2015 at 12:37 PM, Bhavesh Mistry <mistry.p.bhav...@gmail.com> wrote: > Hi Kafka Dev Team, > > I am following-up with you guys regarding New (Java) Producer behavior in > event of network or firewall rules. I just wanted to make Java Producer > resilient of any network or firewall issues, and does not become > single-point of failure in application: > > 1) Jira Issue https://issues.apache.org/jira/browse/KAFKA-1788 > > > https://issues.apache.org/jira/browse/KAFKA-1788?focusedCommentId=14259235&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14259235 > > What should be the behavior of the Producer when it can not reach leader > broker, but metadata reported broker is leader for that partition (via > other broker) ? Should the record-error-rate be counted and Call Back > should be called with error or not ? > > 1) *record-error-rate* metric remain zero despite following firewall > rule. In my opinion, it should have called > org.apache.kafka.clients.producer.Callback but I did not see that happening > either one or two are brokers not reachable. > > 2) Is jira ticket https://issues.apache.org/jira/browse/KAFKA-1788 will > be merged to 0.8.2 ? This will give the ability to close the producer in > event of lost connectivity to broker if io thread misbehave (does not end) > ? > > Thanks for your help ! > > Thanks, > Bhavesh >
