ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
Date Tue, 05 Mar 2019 15:19:00 GMT

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

Ignite TC Bot commented on IGNITE-11465:
----------------------------------------

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=3240114]]
* IgnitePdsWithIndexingCoreTestSuite: IgnitePdsBinaryMetadataOnClusterRestartTest.testNewBinaryMetadataIsPropagatedToAllOutOfDataNodes
- 0,0% fails in last 449 master runs.

{color:#d04437}MVCC Cache 7{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=3241610]]
* IgniteCacheMvccTestSuite7: GridCacheRebalancingPartitionCountersMvccTest.test - 0,0% fails
in last 448 master runs.

{color:#d04437}PDS 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=3240116]]
* IgnitePdsTestSuite: IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateDuringEvictionAndRebalance
- 0,0% fails in last 443 master runs.

{color:#d04437}Activate / Deactivate Cluster{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=3241612]]
* IgniteStandByClusterSuite: CacheBaselineTopologyTest.testAffinityAssignmentChangedAfterRestart
- 0,0% fails in last 445 master runs.

{color:#d04437}PDS 4{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=3241614]]
* IgnitePdsTestSuite4: ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions
- 0,0% fails in last 443 master runs.
* IgnitePdsTestSuite4: IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testDeactivateDuringEvictionAndRebalance
- 0,0% fails in last 443 master runs.

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3233491&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Multiple client leave/join events may wipe affinity assignment history and cause transactions
fail
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11465
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11465
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Rakov
>            Assignee: Ivan Rakov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity assignments. However,
flood of client joins/leaves may wipe it out entirely and cause fail/hang of transaction that
was started before the flood due to the following exception:
> {code:java}
>             if (cache == null || cache.topologyVersion().compareTo(topVer) > 0) {
>                 throw new IllegalStateException("Getting affinity for topology version
earlier than affinity is " +
>                     "calculated [locNode=" + ctx.discovery().localNode() +
>                     ", grp=" + cacheOrGrpName +
>                     ", topVer=" + topVer +
>                     ", head=" + head.get().topologyVersion() +
>                     ", history=" + affCache.keySet() +
>                     ']');
>             }
> {code}
> History is limited in order to prevent JVM heap overflow. At the same time, only "server
event" affinity assignments are heavy: "client event" assignments are just shallow copies
of "server event" assignments.
> I suggest to limit history by the number of "server event" assignments.
> Also, considering the provided fix, I don't see any need to keep 500 items in history.
I propose to change history size to 50.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message