[ https://issues.apache.org/jira/browse/KAFKA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-339: -------------------------- Status: Patch Available (was: Open) Uploaded patch v1. Created an AbstractFetcher and AbstractFetcherManager, which contain the common code path for fetchers used in followers and real consumer clients. Added ReplicaFetcher and ReplicaFetcherManager (use multi-fetch) to replace ReplicaFetcherThread. Will reimplement the fetcher in consumer client based on AbstractFetcher and AbstractFetcherManager in a separate jira, kafka-362. > using MultiFetch in the follower > -------------------------------- > > Key: KAFKA-339 > URL: https://issues.apache.org/jira/browse/KAFKA-339 > Project: Kafka > Issue Type: Sub-task > Components: core > Affects Versions: 0.8 > Reporter: Jun Rao > Assignee: Jun Rao > Fix For: 0.8 > > Attachments: kafka-339_v1.patch > > Original Estimate: 252h > Remaining Estimate: 252h > > A broker could be following multiple topic/partitions from the broker. > Instead of using 1 fetcher thread per topic/partition, it would be more > efficient to use 1 fetcher thread that issues multi-fetch requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira