hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Zhong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-7824) Improve master start up time when there is log splitting work
Date Tue, 09 Apr 2013 01:17:14 GMT

     [ https://issues.apache.org/jira/browse/HBASE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeffrey Zhong updated HBASE-7824:
---------------------------------

    Attachment: hbase-7824-v10.patch

Submit v10 patch to incorporate feedbacks from Chunhui and Ram.

After I moved enableSSHForRoot() right after rootAssignment. I can run TestMasterFailover
10 times in a loop successfully while there may be one failure before.

{code}
Test Suite Result:

Tests run: 1339, Failures: 0, Errors: 0, Skipped: 13

Integration Test: IntegrationTestDataIngestWithChaosMonkey

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 662.064 sec
{code}
                
> Improve master start up time when there is log splitting work
> -------------------------------------------------------------
>
>                 Key: HBASE-7824
>                 URL: https://issues.apache.org/jira/browse/HBASE-7824
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.94.8
>
>         Attachments: hbase-7824.patch, hbase-7824-v10.patch, hbase-7824_v2.patch, hbase-7824_v3.patch,
hbase-7824-v7.patch, hbase-7824-v8.patch, hbase-7824-v9.patch
>
>
> When there is log split work going on, master start up waits till all log split work
completes even though the log split has nothing to do with meta region servers.
> It's a bad behavior considering a master node can run when log split is happening while
its start up is blocking by log split work. 
> Since master is kind of single point of failure, we should start it ASAP.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message