[
https://issues.apache.org/jira/browse/HADOOP-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547574#comment-16547574
]
Weiwei Yang commented on HADOOP-15614:
--------------------------------------
Hi [~kihwal]/[~jlowe]
The test was trying to verify when there is an exception thrown during
refreshing the cache, client can still get old value immediately. Right after
#1 the cache will be starting to refresh, and it takes the bets on the refresh
will be finished AFTER execution of #2.
{code}
#1 timer.advance(4 * 1000);
#2 assertEquals(startingRequestCount, FakeGroupMapping.getRequestCount());
{code}
Those small sleeps \{{Thread.sleep(50)}} have similar issue.
Instead of counting on timing, I uploaded a patch that similar to HADOOP-13375.
That fixes this issue, please take a look if that makes sense.
Thanks
> TestGroupsCaching.testExceptionOnBackgroundRefreshHandled reliably fails
> ------------------------------------------------------------------------
>
> Key: HADOOP-15614
> URL: https://issues.apache.org/jira/browse/HADOOP-15614
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Kihwal Lee
> Priority: Major
>
> When {{testExceptionOnBackgroundRefreshHandled}} is run individually, it
> reliably fails. It seems like a fundamental bug in the test or groups caching.
> A similar issue was dealt with in HADOOP-13375. [~cheersyang], do you have
> any insight into this?
> This test case was added in HADOOP-13263.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
