replication status

The remaining jiras for 0.8 are listed in the following dashboard. We will be focusing on the blocker jiras first. Contributions are welcome. We hope to have an early version for people to try out in mid to late Oct. https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+development

replication status

Thanks to Joel Koshy, we now have a dashboard for tracking the remaining jiras of Kafka replication. We welcome contributions from the community. https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+development We closed a few jiras this week, the largest of which is kafka-385: jmx

Replication status

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_

Re: Replication status

Thanks for the status update. > The following jiras can be worked on in parallel and we welcome > contribution from the community. > > KAFKA-385: RequestPurgatory enhancements > I started on the above, although got side-tracked with some other work. Will get back to it next week. Joel

replication status

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

replication status

Hi, We didn't close any jira this week, but have patch under review for the following jiras. 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 maintenanc

replication status

Hi, We closed the following jiras this week. KAFKA-339: Use multi-fetch for follower replication KAFKA-353: Tie Producer-side ack with high watermark and progress of replicas We have people signed up on the following jiras: KAFKA-350: Improve the highwatermark maintenance to handle failures KAFKA

replication status

Hi, We closed the following jira this week. A few other jiras have patches and are under review. KAFKA-329: Create topic support (revisit based on v3 design) We have people signed up on the following jiras: KAFKA-339: Use multi-fetch for follower replication KAFKA-350: Improve the highwatermark

Re: Replication status

Sounds great ! Thanks, Neha On Fri, Jun 15, 2012 at 2:08 PM, Joe Stein wrote: > I can start working on > > KAFKA-354: refactor setter/getter in scala style > > I will assign the JIRA to myself later tonight/tomorrow > > On Fri, Jun 15, 2012 at 3:41 PM, Neha Narkhede wrote: > >> Hi, >> >> As of t

Re: Replication status

I can start working on KAFKA-354: refactor setter/getter in scala style I will assign the JIRA to myself later tonight/tomorrow On Fri, Jun 15, 2012 at 3:41 PM, Neha Narkhede wrote: > Hi, > > As of this week, we closed: > > KAFKA-335: Embedded controller > KAFKA-341: Create a new single host sy

Replication status

Hi, As of this week, we closed: KAFKA-335: Embedded controller KAFKA-341: Create a new single host system test to validate all replicas on 0.8 branch We have people signed up on the following jiras: KAFKA-329: Create topic support (revisit based on v3 design) KAFKA-339: Use multi-fetch for foll

kafka replication status

Hi, As of this week, we closed KAFKA-336 (for controller to send requests to brokers). We have people signed up on the following jiras: KAFKA-335: Embedded controller KAFKA-329: Create topic support (revisit based on v3 design) KAFKA-339: Use multi-fetch for follower replication The following j

kafka replication status

Hi, As of this week, we closed 2 big jiras: kafka-46 (commit thread) and kafka-348 (merge from trunk). Basic replication (without failure) is working now. We have people signed up on the following jiras: KAFKA-336: Admin RPC between controller and broker KAFKA-335: Embedded controller KAFKA-329: