[
https://issues.apache.org/jira/browse/PHOENIX-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934466#comment-13934466
]
James Taylor commented on PHOENIX-849:
--------------------------------------
+1. Thanks for tracking this down, [~jeffreyz]
> Test StatsManagerIT#testStatsManager is flaky
> ----------------------------------------------
>
> Key: PHOENIX-849
> URL: https://issues.apache.org/jira/browse/PHOENIX-849
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jeffrey Zhong
> Attachments: phoenix-849.patch
>
>
> You will see it fails if you run it 10 times in a loop. Below is the error
> stack trace:
> {code}
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.phoenix.end2end.StatsManagerTest.testStatsManager(StatsManagerTest.java:136)
> {code}
> The root cause is that the constructor MinKeyChange & MaxKeyChange internally
> trigger the states update
> {code}
> MinKeyChange minKeyChange = new MinKeyChange(stats, table);
> MaxKeyChange maxKeyChange = new MaxKeyChange(stats, table);
> {code}
> So the latter {code}stats.getMinKey(table);{code} gets a different value
> unexpectedly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
