[
https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144229#comment-15144229
]
Semen Boikov commented on IGNITE-2565:
--------------------------------------
Rebalanced topology version is updated asynchronously from exchange worker
thread (after exchange future is done). It is safe to add code updating
rebalanced topology version in 'GridDhtPartitionTopology.beforeExchange', so it
will be updated before initial exchnage is done and Ignite API can be used.
> TCK fails when client nodes are particapating in the cluster.
> -------------------------------------------------------------
>
> Key: IGNITE-2565
> URL: https://issues.apache.org/jira/browse/IGNITE-2565
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Anton Vinogradov
> Assignee: Semen Boikov
> Priority: Critical
> Labels: important
> Fix For: 1.6
>
>
> TCK suite fail periodically fails with assetrions about CacheHitPercentage.
> I see that a lot of changes was made last two months where added logic with
> invoking of metrics.onRead(); possible this affects statictic counting.
> Typical stacktrace:
> java.lang.AssertionError: expected:<100.0> but was:<50.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
