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 (Commented) (JIRA)" <ji...@apache.org> on 2012/03/02 02:36:57 UTC
[jira] [Commented] (KAFKA-46) Commit thread, ReplicaFetcherThread
for intra-cluster replication
[ https://issues.apache.org/jira/browse/KAFKA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220583#comment-13220583 ]
Neha Narkhede commented on KAFKA-46:
------------------------------------
>> Should this be broken down into two sub tasks: One for the commiting thread on the leader and one for the fetcher thread on the follower?
Lets not worry about that for now. I'll take care of this JIRA, once we resolve the other JIRAs. This one has many other dependencies.
> 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
>
> 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