[
https://issues.apache.org/jira/browse/HBASE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HBASE-4742:
-------------------------------
Attachment: D237.5.patch
Liyin updated the revision "[jira] [HBASE-4742] Split dead server's log in
parallel".
Reviewers: Kannan, khemani, Karthik, mbautin, JIRA
Address Mikhail and Kannan's comments for using thread pool to bound the
total number thread.
The default max thread is 1000.
Also keep testing it on the dev cluster.
REVISION DETAIL
https://reviews.facebook.net/D237
AFFECTED FILES
src/main/java/org/apache/hadoop/hbase/master/HMaster.java
src/main/java/org/apache/hadoop/hbase/master/ProcessServerShutdown.java
src/main/java/org/apache/hadoop/hbase/master/RegionServerOperationQueue.java
src/test/java/org/apache/hadoop/hbase/master/TestMultiRegionServerShutDown.java
> Split dead server's log in parallel
> -----------------------------------
>
> Key: HBASE-4742
> URL: https://issues.apache.org/jira/browse/HBASE-4742
> Project: HBase
> Issue Type: Improvement
> Reporter: Liyin Tang
> Assignee: Liyin Tang
> Attachments: D237.1.patch, D237.2.patch, D237.3.patch, D237.4.patch,
> D237.5.patch
>
>
> When one region server goes down, the master will shutdown the region server
> and split its log.
> However, splitting log is a blocking call and it would take some time.
> If more than one region server go down, the master will split its log one by
> one, which is not efficient.
> Since we have the distributed log split, we could split these logs from the
> dead servers in parallel.
--
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
