[
https://issues.apache.org/jira/browse/KAFKA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616361#comment-13616361
]
Jun Rao commented on KAFKA-253:
-------------------------------
No. Since most of the development happens on 0.8, we are only fixing blocker
issues in 0.7.
> Refactor the async producer to have only one queue instead of one queue per
> broker in a Kafka cluster
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-253
> URL: https://issues.apache.org/jira/browse/KAFKA-253
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Fix For: 0.8
>
> Attachments: kafka-253.patch, kafka-253_v2.patch, kafka-253_v3.patch,
> kafka-253_v4.patch, kafka-253_v5.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Today, the async producer is associated with a particular broker instance,
> just like the SyncProducer. The Producer maintains a producer pool of
> sync/async producers, one per broker. Since the producer pool creates one
> async producer per broker, we have multiple producer queues for one Producer
> instance.
> With replication, a topic partition will be logical. This requires
> refactoring the AsyncProducer to be broker agnostic. As a side effect of this
> refactoring, we should also ensure that we have only one queue per Producer
> instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
