[
https://issues.apache.org/jira/browse/HBASE-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi resolved HBASE-11684.
-----------------------------------
Resolution: Duplicate
Assignee: (was: Tianying Chang)
Duplicate of HBASE-12988
> HBase replicationSource should support multithread to ship the log entry
> ------------------------------------------------------------------------
>
> Key: HBASE-11684
> URL: https://issues.apache.org/jira/browse/HBASE-11684
> Project: HBase
> Issue Type: Improvement
> Components: Performance, Replication
> Reporter: Tianying Chang
>
> We found the replication rate cannot keep up with the write rate when the
> master cluster is write heavy. We got huge log queue build up due to that.
> But when we do a rolling restart of master cluster, we found that the
> appliedOpsRate doubled due to the extra thread created to help recover the
> log of the restarted RS. ReplicateLogEntries is a synchronous blocking call,
> it becomes the bottleneck when is only runs with one thread. I think we
> should support multi-thread for the replication source to ship the data. I
> don't see any consistency problem. Any other concern here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)