[ 
https://issues.apache.org/jira/browse/HBASE-14962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-14962:
--------------------------
    Attachment: 14962.patch

Test gets RS and from here, it gets actual Region, doctors it so it can be 
spied upon and then puts the spied upon Region back into RS list-of-regions. 
This latter was being done by just getting the key of the 'first region'. 
Sometimes the latter was hbase:meta.

> TestSplitWalDataLoss fails on all branches
> ------------------------------------------
>
>                 Key: HBASE-14962
>                 URL: https://issues.apache.org/jira/browse/HBASE-14962
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Elliott Clark
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: 14962.patch, 
> org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss-output.txt, 
> org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss-output.txt
>
>
> With some regularity I am seeing: 
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
> action: TestSplitWalDataLoss:dataloss: 1 time, 
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.makeException(AsyncProcess.java:228)
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.access$1800(AsyncProcess.java:208)
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess.waitForAllPreviousOpsAndReset(AsyncProcess.java:1712)
>       at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.backgroundFlushCommits(BufferedMutatorImpl.java:240)
>       at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.flush(BufferedMutatorImpl.java:190)
>       at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1430)
>       at org.apache.hadoop.hbase.client.HTable.put(HTable.java:1021)
>       at 
> org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss.test(TestSplitWalDataLoss.java:121)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to