You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/04/12 09:56:00 UTC
[jira] [Commented] (HBASE-26946) TestRetainAssignmentOnRestartSplitWithoutZk infinite loop
[ https://issues.apache.org/jira/browse/HBASE-26946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521053#comment-17521053 ]
Duo Zhang commented on HBASE-26946:
-----------------------------------
[~busbey] FYI.
> TestRetainAssignmentOnRestartSplitWithoutZk infinite loop
> ---------------------------------------------------------
>
> Key: HBASE-26946
> URL: https://issues.apache.org/jira/browse/HBASE-26946
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Reporter: Duo Zhang
> Priority: Major
>
> {noformat}
> 2022-04-05T01:56:10,567 ERROR [Thread-350] server.NIOServerCnxnFactory$1(92): Thread Thread[Thread-350,5,FailOnTimeoutGroup] died
> java.lang.IllegalThreadStateException: null
> at java.lang.Thread.start(Thread.java:794) ~[?:?]
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.startWorkers(ProcedureExecutor.java:616) ~[classes/:?]
> at org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1666) ~[classes/:?]
> at org.apache.hadoop.hbase.master.TestRetainAssignmentOnRestart$HMasterForTest.access$101(TestRetainAssignmentOnRestart.java:57) ~[test-classes/:?]
> at org.apache.hadoop.hbase.master.TestRetainAssignmentOnRestart$HMasterForTest.lambda$startProcedureExecutor$0(TestRetainAssignmentOnRestart.java:70) ~[test-classes/:?]
> at java.lang.Thread.run(Thread.java:834) ~[?:?]
> 2022-04-05T01:56:10,570 INFO [RS:2;4d77efa4cf73:37349] regionserver.HRegionServer(1179): stopping server 4d77efa4cf73,37349,1649123763933
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [RS:2;4d77efa4cf73:37349] ipc.AbstractRpcClient(505): Stopping rpc client
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 INFO [RS:2;4d77efa4cf73:37349] regionserver.HRegionServer(1529): Waiting on 1 regions to close
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [RS:2;4d77efa4cf73:37349] regionserver.HRegionServer(1533): Online Regions={3b6c92c681d8cf1316520e3a89546fe0=restartTableThree,,1649123769361.3b6c92c681d8cf1316520e3a89546fe0.}
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> 2022-04-05T01:56:10,570 DEBUG [PEWorker-5] procedure2.AbstractProcedureScheduler(158): the scheduler is not running
> {noformat}
> After a strange exception then we enter an infinite loop and output a lot of log messages which eat all the spaces...
--
This message was sent by Atlassian Jira
(v8.20.1#820001)