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

Jeffrey Zhong updated HBASE-9255:
---------------------------------

    Attachment: hbase-9255.patch
    
> TestAsyncProcess#testErrorsServers is flaky on suse linux
> ---------------------------------------------------------
>
>                 Key: HBASE-9255
>                 URL: https://issues.apache.org/jira/browse/HBASE-9255
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.98.0, 0.95.2
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>            Priority: Minor
>             Fix For: 0.98.0, 0.96.0
>
>         Attachments: hbase-9255.patch
>
>
> TestAsyncProcess#testErrorsServers fails quite frequently on Suse because 
> HTable.WriteBufferSize is NOT set so the test may fail at HTable.put command 
> where backgroundFlushCommits kicks in.
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
> action: Exception: 1 time, 
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.makeException(AsyncProcess.java:161)
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.access$500(AsyncProcess.java:149)
>       at 
> org.apache.hadoop.hbase.client.AsyncProcess.getErrors(AsyncProcess.java:707)
>       at 
> org.apache.hadoop.hbase.client.HTable.backgroundFlushCommits(HTable.java:911)
>       at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:878)
>       at org.apache.hadoop.hbase.client.HTable.put(HTable.java:840)
>       at 
> org.apache.hadoop.hbase.client.TestAsyncProcess.testErrorsServers(TestAsyncProcess.java:603)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to