You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Umesh Kumar Kumawat (Jira)" <ji...@apache.org> on 2025/08/28 06:37:00 UTC

[jira] [Created] (HBASE-29555) TestRollbackSCP.testFailAndRollback fails sometime because non empty Scheduler queue

Umesh Kumar Kumawat created HBASE-29555:
-------------------------------------------

             Summary: TestRollbackSCP.testFailAndRollback fails sometime because non empty Scheduler queue 
                 Key: HBASE-29555
                 URL: https://issues.apache.org/jira/browse/HBASE-29555
             Project: HBase
          Issue Type: Bug
          Components: Scheduler
    Affects Versions: 2.6.3
            Reporter: Umesh Kumar Kumawat
            Assignee: Umesh Kumar Kumawat


In some of PR validation/build I noticed that TestRollbackSCP.testFailAndRollback fails. Below are the exception/ stack trace
{code:java}
java.lang.IllegalArgumentException: scheduler queue not empty: MasterProcedureScheduler[running=true,tableMap=TableQueue[key=hbase:namespace,lockStatus=LockAndQueue[exclusiveLock=false,sharedLockCount=0],size=1,namespaceLockStatus=LockAndQueue[exclusiveLock=false,sharedLockCount=0]],tableWaitingMap={},peerMap=<null>,metaMap=<null>]
	at org.apache.hbase.thirdparty.com.google.common.base.Preconditions.checkArgument(Preconditions.java:217)	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:340)	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:665)	at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.restart(ProcedureTestingUtility.java:132)	at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.restart(ProcedureTestingUtility.java:100)	at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.restartMasterProcedureExecutor(MasterProcedureTestingUtility.java:83)	at org.apache.hadoop.hbase.master.assignment.TestRollbackSCP.testFailAndRollback(TestRollbackSCP.java:180)	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {code}
I was able to reproduce it on local. Will debug further.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)