[ https://issues.apache.org/jira/browse/HBASE-26998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HBASE-26998 started by Yu Li. ------------------------------------- > TestRegionProcessRowsWithLocks#testProcessExceptionAndRollBack is broken in > branch-1 > ------------------------------------------------------------------------------------ > > Key: HBASE-26998 > URL: https://issues.apache.org/jira/browse/HBASE-26998 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 1.7.1 > Reporter: Yu Li > Assignee: Yu Li > Priority: Major > > As titled, I found that > {{TestRegionProcessRowsWithLocks#testProcessExceptionAndRollBack}} is broken > while reviewing the PR for HBASE-26977 ([pre-commit test log > here|https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4377/7/artifact/out/patch-unit-hbase-server.txt]) > with below exceptions: > {noformat} > [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 10.166 s <<< FAILURE! - in > org.apache.hadoop.hbase.regionserver.TestRegionProcessRowsWithLocks > [ERROR] > testProcessExceptionAndRollBack(org.apache.hadoop.hbase.regionserver.TestRegionProcessRowsWithLocks) > Time elapsed: 5.849 s <<< ERROR! > com.google.protobuf.ServiceException: Error calling method > hbase.pb.RowProcessorService.Process > at > org.apache.hadoop.hbase.ipc.CoprocessorRpcChannel.callBlockingMethod(CoprocessorRpcChannel.java:75) > at > org.apache.hadoop.hbase.protobuf.generated.RowProcessorProtos$RowProcessorService$BlockingStub.process(RowProcessorProtos.java:1631) > at > org.apache.hadoop.hbase.regionserver.TestRegionProcessRowsWithLocks.incrementCounter(TestRegionProcessRowsWithLocks.java:193) > at > org.apache.hadoop.hbase.regionserver.TestRegionProcessRowsWithLocks.testProcessExceptionAndRollBack(TestRegionProcessRowsWithLocks.java:173) > {noformat} > Manually test the single case in my local environment also failed. Using > {{git bisect}}, I found the issue was introduced by HBASE-26393 and have been > existing for several months (since Oct 23, 2021). > The fix is straight forward and I will prepare a PR soon. -- This message was sent by Atlassian Jira (v8.20.7#820007)