kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jun Rao <jun...@gmail.com>
Subject replication status
Date Sat, 04 Aug 2012 18:49:53 GMT

We closed 2 jiras this week, of which KAFKA-343 is the last large remaining
jira in phase 2.
KAFKA-343: Leader election, become leader, become follower
KAFKA-384: Fix intermittent test failures and remove unnecessary sleeps

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-181: Log errors for unrecognized config options

We still have a bunch of clean up jiras left for phase 2. The following
jiras can be worked on in parallel and we welcome
contribution from the community.

KAFKA-415: Controller throws NoSuchElementException
KAFKA-416: Controller tests throw several zookeeper errors
KAFKA-420: maintain HW correctly with only 1 replica in ISR
KAFKA-422: LazyInitProducerTest has transient test failure
KAFKA-427, KAFKA-421: LogRecoverTest has transient failure
KAFKA-428: need to update leaderAndISR path in ZK conditionally
KAFKA-433: ensurePartitionLeaderOnThisBroker should not access ZK
KAFKA-434: IllegalMonitorStateException in ReplicaManager.makerFollower
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



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message