[
https://issues.apache.org/jira/browse/HBASE-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735500#comment-16735500
]
Jingyun Tian commented on HBASE-21588:
--------------------------------------
[~zghaobac] I checked the code and found some regionserver was still running
when tear down. Then I found there is a piece of code in tearDown() of
TestServerCrashProcedure:
{code}
if (master != null && master.getMasterProcedureExecutor() != null) {
ProcedureTestingUtility.setKillAndToggleBeforeStoreUpdate(
master.getMasterProcedureExecutor(), false);
}
{code}
Thus I add the same code into TestSplitWalProcedure. Besides this, I make the
test finish after all procedures done, I guess there is some procedure related
thread stuck when we tear down the cluster. But I didn't found that thread from
failed test logs.
> Procedure v2 wal splitting implementation
> -----------------------------------------
>
> Key: HBASE-21588
> URL: https://issues.apache.org/jira/browse/HBASE-21588
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Attachments: HBASE-21588.master.003.patch,
> HBASE-21588.master.004.patch, HBASE-21588.master.005.patch,
> HBASE-21588.master.006.patch, HBASE-21588.master.007.patch,
> HBASE-21588.master.008.patch, HBASE-21588.master.009.patch,
> HBASE-21588.master.010.patch, HBASE-21588.master.011.patch,
> HBASE-21588.master.012.patch, HBASE-21588.master.013.patch,
> HBASE-21588.master.014.patch, HBASE-21588.master.015.patch,
> HBASE-21588.master.016.patch, HBASE-21588.master.017.patch,
> HBASE-21588.master.018.patch, HBASE-21588.master.018.patch,
> HBASE-21588.master.019.patch, HBASE-21588.master.019.patch,
> HBASE-21588.master.020.patch
>
>
> create a sub task to submit the implementation of procedure v2 wal splitting
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
