Hi, We closed 5 jiras this week -
KAFKA-350: Enable message replication in the presence of controlled failures KAFKA-405 Improve high watermark maintenance to store high watermarks in a single file KAFKA-412 deal with empty TopicData list in producer and fetch request KAFKA-413 single_host_multi_brokers system test fails on laptop KAFKA-418 NullPointerException in ConsumerFetcherManager We have patch under review for the following jira - KAFKA-343: Leader election, become leader, become follower We have people signed up on the following jiras: KAFKA-354: refactor setter/getter in scala style KAFKA-376: expose different data to fetch requests from the follower replicas and consumer clients KAFKA-386: Race condition in accessing ISR KAFKA-385: RequestPurgatory enhancements KAFKA-369: remove ZK dependency on producer KAFKA-384: Fix intermittent test failures and remove unnecessary sleeps With KAFKA-350 resolved, message replication is possible in the presence of broker side failures. We will now focus on building a system test suite to add more performance/regression tests The following jiras can be worked on in parallel and we welcome contribution from the community. 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-356: create a generic thread class Thanks, Neha
