hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8290) TestHTableMultiplexer is flaky
Date Tue, 09 Apr 2013 11:38:22 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626502#comment-13626502
] 

Hudson commented on HBASE-8290:
-------------------------------

Integrated in HBase-TRUNK #4045 (See [https://builds.apache.org/job/HBase-TRUNK/4045/])
    HBASE-8290  TestHTableMultiplexer is flaky (Revision 1465912)

     Result = SUCCESS
nkeywal : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHTableMultiplexer.java

                
> TestHTableMultiplexer is flaky
> ------------------------------
>
>                 Key: HBASE-8290
>                 URL: https://issues.apache.org/jira/browse/HBASE-8290
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.95.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: 8290.v1.patch
>
>
> I reproduce it all the time if I comment the sleep here:
> {code}
>   private void verifyAllBufferedPutsHaveFlushed(HTableMultiplexerStatus status) {
>     int retries = 8;
>     int tries = 0;
>     do {         /*
>       try {
>         Thread.sleep(2 * TEST_UTIL.getConfiguration().getLong(
>           HTableMultiplexer.TABLE_MULTIPLEXER_FLUSH_FREQ_MS, 100));
>         tries++;
>       } catch (InterruptedException e) {
>         Thread.currentThread().interrupt();
>       }         */
>     } while (status.getTotalBufferedCounter() != 0 && tries != retries);
>     assertEquals("There are still some buffered puts left in the queue",
>         0, status.getTotalBufferedCounter());
>   }
> {code}
> Given that getTotalBufferedCounter is never decremented, there is a misunderstanding
somewhere. As well, reading plain values without a volatile or a synchronized in a MT context
is likely to be wrong.

--
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

Mime
View raw message