Discussion:
[jira] [Created] (HBASE-21562) TestRestoreSnapshotFromClientAfterSplittingRegions and related tests are flakey
stack (JIRA)
2018-12-06 19:03:00 UTC
Permalink
stack created HBASE-21562:
-----------------------------

Summary: TestRestoreSnapshotFromClientAfterSplittingRegions and related tests are flakey
Key: HBASE-21562
URL: https://issues.apache.org/jira/browse/HBASE-21562
Project: HBase
Issue Type: Bug
Components: test
Reporter: stack
Fix For: 2.1.2


Fails 60% of the time on GCE runs. Messes up our nightlies for branch-2.1 and branch-2.0 at least.

Looking its a bit tough figuring what is going on. Test asks us split regions. The split starts then hangs. Last thing reported is:

2018-12-06 10:20:30,823 INFO [PEWorker-16] procedure.MasterProcedureScheduler(741): Took xlock for pid=174, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure table=testRestoreSnapshotAfterSplittingRegions_1__regionReplication_3_-1544120421990, parent=034bb3ebb3f9a7442f927caacdda5354, daughterA=fbe392ca659b3913181d05ac4fb19b4c, daughterB=3646ac333722af33c32e6f3428d23f95

... then all we get is that the worker is stuck.





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
stack (JIRA)
2018-12-07 04:49:00 UTC
Permalink
[ https://issues.apache.org/jira/browse/HBASE-21562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-21562.
---------------------------
Resolution: Duplicate

Resolve. Duplicate of HBASE-21559. Thanks [~Apache9]
Post by stack (JIRA)
TestRestoreSnapshotFromClientAfterSplittingRegions and related tests are flakey
-------------------------------------------------------------------------------
Key: HBASE-21562
URL: https://issues.apache.org/jira/browse/HBASE-21562
Project: HBase
Issue Type: Bug
Components: test
Reporter: stack
Priority: Major
Fix For: 2.1.2
Fails 60% of the time on GCE runs. Messes up our nightlies for branch-2.1 and branch-2.0 at least.
2018-12-06 10:20:30,823 INFO [PEWorker-16] procedure.MasterProcedureScheduler(741): Took xlock for pid=174, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure table=testRestoreSnapshotAfterSplittingRegions_1__regionReplication_3_-1544120421990, parent=034bb3ebb3f9a7442f927caacdda5354, daughterA=fbe392ca659b3913181d05ac4fb19b4c, daughterB=3646ac333722af33c32e6f3428d23f95
... then all we get is that the worker is stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Loading...