You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2012/06/01 03:31:23 UTC
[jira] [Updated] (KAFKA-46) Commit thread, ReplicaFetcherThread for
intra-cluster replication
[ https://issues.apache.org/jira/browse/KAFKA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-46:
-------------------------------
Attachment: kafka-46-v4.patch
Attaching an updated patch that includes the rebase changes from KAFKA-348
Also, updated the follow up JIRAs - KAFKA-350 and KAFKA-351
> Commit thread, ReplicaFetcherThread for intra-cluster replication
> -----------------------------------------------------------------
>
> Key: KAFKA-46
> URL: https://issues.apache.org/jira/browse/KAFKA-46
> Project: Kafka
> Issue Type: Bug
> Reporter: Jun Rao
> Assignee: Neha Narkhede
> Attachments: kafka-46-draft.patch, kafka-46-v1.patch, kafka-46-v2.patch, kafka-46-v3.patch, kafka-46-v4.patch
>
>
> We need to implement the commit thread at the leader and the fetcher thread at the follower for replication the data from the leader.
--
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