Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.6
-
None
-
None
Description
TcpDiscoveryMultiThreadedTest#testCustomEventNodeRestart (in current codebase muted by renaming to _testCustomEventNodeRestart) fails on Teamcity with unexpected exception (could not reproduce locally):
org.apache.ignite.IgniteException: Getting affinity for topology version earlier than affinity is calculated [locNode=TcpDiscoveryNode [id=ae293efb-8b41-4b86-b32b-747070800001, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47502], discPort=47502, order=14, intOrder=10, lastExchangeTime=1542188985763, loc=true, ver=2.7.0#20181113-sha1:b186327e, isClient=false], grp=default, topVer=AffinityTopologyVersion [topVer=17, minorTopVer=0], head=AffinityTopologyVersion [topVer=18, minorTopVer=0], history=[AffinityTopologyVersion [topVer=14, minorTopVer=0], AffinityTopologyVersion [topVer=15, minorTopVer=0], AffinityTopologyVersion [topVer=18, minorTopVer=0]]] Caused by: javax.cache.CacheException: Getting affinity for topology version earlier than affinity is calculated [locNode=TcpDiscoveryNode [id=ae293efb-8b41-4b86-b32b-747070800001, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet
More detailed teamcity logs are attached: TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.log and TcpDiscoveryMultiThreadedTest.testCustomEventNodeRestart.2.log
Attachments
Attachments
Issue Links
- duplicates
-
IGNITE-11465 Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
- Resolved
- is related to
-
IGNITE-10200 GridCacheSetAbstractSelfTest#testMultipleStructuresInDifferentGroups and some other tests are incorrectly muted (by underscore prefix in name)
- Resolved
-
IGNITE-12014 Getting affinity for topology version earlier than affinity is calculated for system cache
- Resolved
-
IGNITE-3418 TcpDiscoverySpi: lots of duplicated node failed messages
- Closed