[
https://issues.apache.org/jira/browse/IGNITE-8508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8508:
-----------------------------------
Fix Version/s: (was: 2.6)
2.7
> Zookeeper discovery SPI may notify custom message ACK with out-of-order
> topology version
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-8508
> URL: https://issues.apache.org/jira/browse/IGNITE-8508
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
> Fix For: 2.7
>
>
> I observed the following assertion in one of my tests.
> {code}
> java.lang.AssertionError: Topology version out of order [this.topVer=Snapshot
> [topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0]], topVer=4,
> node=ZookeeperClusterNode [id=2933aa95-0161-4a0d-aad8-274a7b887fae,
> addrs=[172.25.1.30, 172.17.0.1, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=1,
> loc=true, client=false], nextTopVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:746)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.notifyCustomEvent(ZookeeperDiscoveryImpl.java:3428)
> {code}
> The assertion happens because a custom event ACK is generated after another
> discovery message processing, which may lead to the following sequence of
> events:
> {code}
> Custom event (5, 1)
> Node Failed (6, 0)
> Custom event ACK (5, 1)
> {code}
> The root cause is ZK discovery using the original message topology version
> for notification. TCP discovery uses current ring topology version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
