[ 
https://issues.apache.org/jira/browse/HBASE-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177586#comment-16177586
 ] 

Phil Yang commented on HBASE-17432:
-----------------------------------

Remove fix version as we may not get it in before 2.0 release, thanks.

> Use less threads to read WAL in replication
> -------------------------------------------
>
>                 Key: HBASE-17432
>                 URL: https://issues.apache.org/jira/browse/HBASE-17432
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>
> Now for each peer and each failover source we use different threads to read 
> WAL, which means one WAL file will be read many times if we have many peers. 
> We can read logs in one thread and push them to peers concurrently.
> Some cases should be considered. For example, if one of peers is stuck, the 
> reading thread should kick it out of concurrent peers and use an independent 
> thread to read logs for this peer just like old style. If finally this peer's 
> progress catch up other peers, they can be merged back.
> Of course, failover threads should still be independent because they read 
> different WAL files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to