[
https://issues.apache.org/jira/browse/HBASE-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449277#comment-13449277
]
Jimmy Xiang commented on HBASE-6715:
------------------------------------
Thanks for the review. This is a little clean up. My guess is that the
executor service is not shutdown completely. However, I could not reproduce
it, so I just added some checking to make sure the cache hit count is
stabilized before moving ahead, which should have fix the issue, unless the
cache is still in use after quite some time.
> TestFromClientSide.testCacheOnWriteEvictOnClose is flaky
> --------------------------------------------------------
>
> Key: HBASE-6715
> URL: https://issues.apache.org/jira/browse/HBASE-6715
> Project: HBase
> Issue Type: Test
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Attachments: trunk-6715.patch
>
>
> Occasionally, this test fails:
> {noformat}
> expected:<2049> but was:<2069>
> Stacktrace
> java.lang.AssertionError: expected:<2049> but was:<2069>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at
> org.apache.hadoop.hbase.client.TestFromClientSide.testCacheOnWriteEvictOnClose(TestFromClientSide.java:4248)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
> It could be because there is other thread still accessing the cache.
--
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
