[jira] [Created] (KAFKA-15686) Consumer should be able to detect network problem
Jiahongchao created KAFKA-15686: --- Summary: Consumer should be able to detect network problem Key: KAFKA-15686 URL: https://issues.apache.org/jira/browse/KAFKA-15686 Project: Kafka Issue Type: New Feature Components: consumer Affects Versions: 3.5.0 Reporter: Jiahongchao When we call poll method in consumer, it will return normally even if some partitions do not have a leader. What should we do to detect such failures? Currently we have to check log to find out broker connection problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue
[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiahongchao updated KAFKA-3042: --- Issue Type: Bug (was: Improvement) > updateIsr should stop after failed several times due to zkVersion issue > --- > > Key: KAFKA-3042 > URL: https://issues.apache.org/jira/browse/KAFKA-3042 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8.2.1 > Environment: jdk 1.7 > centos 6.4 >Reporter: Jiahongchao > > sometimes one broker may repeatly log > "Cached zkVersion 54 not equal to that in zookeeper, skip updating ISR" > I think this is because the broker consider itself as the leader in fact it's > a follower. > So after several failed tries, it need to find out who is the leader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue
Jiahongchao created KAFKA-3042: -- Summary: updateIsr should stop after failed several times due to zkVersion issue Key: KAFKA-3042 URL: https://issues.apache.org/jira/browse/KAFKA-3042 Project: Kafka Issue Type: Improvement Affects Versions: 0.8.2.1 Environment: jdk 1.7 centos 6.4 Reporter: Jiahongchao sometimes one broker may repeatly log "Cached zkVersion 54 not equal to that in zookeeper, skip updating ISR" I think this is because the broker consider itself as the leader in fact it's a follower. So after several failed tries, it need to find out who is the leader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-369) remove ZK dependency on producer
[ https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589225#comment-14589225 ] Jiahongchao edited comment on KAFKA-369 at 10/21/15 9:43 AM: - So In producer we need a "metadata.broker.list" string, and in consumer we need a different zookeeper connect string, quite confusing...I want only one string for both of them... was (Author: ihavenoem...@163.com): So In producer we need a "metadata.broker.list: string, and in consumer we need another zookeeper connect string, not perfect... > remove ZK dependency on producer > > > Key: KAFKA-369 > URL: https://issues.apache.org/jira/browse/KAFKA-369 > Project: Kafka > Issue Type: Sub-task > Components: core >Affects Versions: 0.8.0 >Reporter: Jun Rao >Assignee: Yang Ye > Fix For: 0.8.0 > > Attachments: kafka_369_v1.diff, kafka_369_v2.diff, kafka_369_v3.diff, > kafka_369_v4.diff, kafka_369_v5.diff, kafka_369_v6.diff, kafka_369_v7.diff, > kafka_369_v8.diff, kafka_369_v9.diff > > Original Estimate: 252h > Remaining Estimate: 252h > > Currently, the only place that ZK is actually used is in BrokerPartitionInfo. > We use ZK to get a list of brokers for making TopicMetadataRequest requests. > Instead, we can provide a list of brokers in the producer config directly. > That way, the producer client is no longer dependant on ZK. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-369) remove ZK dependency on producer
[ https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589225#comment-14589225 ] Jiahongchao commented on KAFKA-369: --- So In producer we need a "metadata.broker.list: string, and in consumer we need another zookeeper connect string, not perfect... > remove ZK dependency on producer > > > Key: KAFKA-369 > URL: https://issues.apache.org/jira/browse/KAFKA-369 > Project: Kafka > Issue Type: Sub-task > Components: core >Affects Versions: 0.8.0 >Reporter: Jun Rao >Assignee: Yang Ye > Fix For: 0.8.0 > > Attachments: kafka_369_v1.diff, kafka_369_v2.diff, kafka_369_v3.diff, > kafka_369_v4.diff, kafka_369_v5.diff, kafka_369_v6.diff, kafka_369_v7.diff, > kafka_369_v8.diff, kafka_369_v9.diff > > Original Estimate: 252h > Remaining Estimate: 252h > > Currently, the only place that ZK is actually used is in BrokerPartitionInfo. > We use ZK to get a list of brokers for making TopicMetadataRequest requests. > Instead, we can provide a list of brokers in the producer config directly. > That way, the producer client is no longer dependant on ZK. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
