Hi, We close the following jira this week. KAFKA-362: ZKConsumerConnector needs to reconnect to new leader after leader change in a partition
The following jiras are under review. KAFKA-343: Leader election, become leader, become follower (v3. A,C) KAFKA-338: controller failover (V3. D) We have people signed up on the following jiras: KAFKA-350: Improve the highwatermark maintenance to handle failures KAFKA-354: refactor setter/getter in scala style KAFKA-376: expose different data to fetch requests from the follower replicas and consumer clients The following jiras can be worked on in parallel and we welcome contribution from the community. KAFKA-386: Race condition in accessing ISR KAFKA-385: RequestPurgatory enhancements KAFKA-369: remove ZK dependency on producer KAFKA-288: rework java producer API KAFKA-289: reuse TopicData when sending produce request KAFKA-391: Producer request and response classes should use maps KAFKA-355: Move the highwatermark maintenance logic out of Log. KAFKA-384: Fix intermittent test failures and remove unnecessary sleeps KAFKA-356: create a generic thread class Thanks, Jun
