[
https://issues.apache.org/jira/browse/HBASE-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741283#comment-14741283
]
stack commented on HBASE-14401:
-------------------------------
Says:
kalashnikov:hbase.git stack$ python ./dev-support/findHangingTests.py
https://builds.apache.org/job/PreCommit-HBASE-Build/15563//consoleText
Fetching the console output from the URL
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient
Hanging test :
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClientWithRegionReplicas
Hanging test : org.apache.hadoop.hbase.client.TestReplicasClient
Hanging test : org.apache.hadoop.hbase.client.TestAdmin2
Hanging test : org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat2
Hanging test : org.apache.hadoop.hbase.mapred.TestTableMapReduceUtil
Hanging test : org.apache.hadoop.hbase.mapred.TestTableSnapshotInputFormat
Hanging test : org.apache.hadoop.hbase.client.TestFromClientSide
Hanging test : org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient
Hanging test : org.apache.hadoop.hbase.client.TestMobSnapshotFromClient
Hanging test : org.apache.hadoop.hbase.client.TestMobSnapshotCloneIndependence
Hanging test : org.apache.hadoop.hbase.util.TestHBaseFsck
Hanging test : org.apache.hadoop.hbase.TestZooKeeper
Printing Failing tests
Failing test : org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Failing test : org.apache.hadoop.hbase.regionserver.TestWALLockup
Looking at the test output it says:
-------------------------------------------------------------------------------
Test set: org.apache.hadoop.hbase.regionserver.TestWALLockup
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.952 sec - in
org.apache.hadoop.hbase.regionserver.TestWALLockup
> Stamp failed appends with sequenceid too.... Cleans up latches
> --------------------------------------------------------------
>
> Key: HBASE-14401
> URL: https://issues.apache.org/jira/browse/HBASE-14401
> Project: HBase
> Issue Type: Sub-task
> Components: test, wal
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 14401.txt, 14401v3.txt, 14401v3.txt, 14401v3.txt
>
>
> Looking in test output I see we can sometimes get stuck waiting on
> sequenceid... The parent issues redo of our semantic makes it so we encounter
> failed append more often around damaged WAL.
> This patch makes it so we stamp sequenceid always, even if the append fails.
> This way all sequenceids are accounted for but more important, the latch on
> sequenceid down in WALKey will be cleared.. where before it was not being
> cleared (there is no global list of outstanding WALKeys waiting on
> sequenceids so no way to clean them up... we don't need such a list if we
> ALWAYS stamp the sequenceid).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
