[
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-v4.patch
The patch is back!
There is one more hanging RIT issue found during tests and I listed below as
item 4.
Patch Contents
==============
Reviewed:
1) Adding support to fast master up
2) Adding a test case for new code
3) Fix test function makehlog to creat rows with keys within assigned region's
key space
New changes in the v4 Patch(unreviewed):
4) Fix ritsGoingToServer hang issue. You can try the new test case
testRSKilledWithMockedOpeningRITGoingToDeadRS in the patch to reproduce the
issue against 0.94 branch.
Basically ritsGoingToServer list doesn't handle disabling or disabled case. You
can see the fix in SSH for details.
[~rajesh23], [~ram_krish] Could you please review this fix? Thanks in advance.
5) Since 0.94 assignment manager is a different animal than 0.96AM, in the
patch I included a config flag "hbase.master.wait.for.log.splitting" to disable
the feature in case some users may desperately need it later.
I'll re-run full suite test and integration tests and post results here.
Is there anyway we can remove some comments in this JIRA otherwise it's hard
for others to follow?
Thanks,
-Jeffrey
> 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_3.patch, hbase-7824.patch,
> hbase-7824_v2.patch, hbase-7824_v3.patch, hbase-7824-v4.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
