kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-369) remove ZK dependency on producer
Date Wed, 21 Oct 2015 20:39:28 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967853#comment-14967853

Jun Rao commented on KAFKA-369:

We are adding a new java consumer (org.apache.kafka.clients.consumer) in trunk and it will
take the same broker list as the producer for bootstrapping.

> 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

View raw message