I have met similar problem too. A node cannot start: WARN 16:08:36.158 [main] org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager: Still waiting for initial partition map exchange [fut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=fa2d0f11-80cf-4891-9533-7a36392157f6, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9463], discPort=9463, order=8, intOrder=6, lastExchangeTime=1496754516085, loc=true, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], topVer=8, nodeId8=fa2d0f11, msg=null, type=NODE_JOINED, tstamp=1496754274106], crd=TcpDiscoveryNode [id=7751c8dc-9bf6-4a21-9ea5-376f2be83913, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9460], discPort=9460, order=1, intOrder=1, lastExchangeTime=1496754273954, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=8, minorTopVer=0], nodeId=fa2d0f11, evt=NODE_JOINED], added=false, initFut=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=true, hash=1259192920], init=true, lastVer=null, partReleaseFut=GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=4, done=true, cancelled=false, err=null, futs=[true, true, true, true]], affChangeMsg=null, skipPreload=false, clientOnlyExchange=false, initTs=1496754276137, centralizedAff=false, changeGlobalStateE=null, exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[bf7a4e48-4867-437b-9cc5-dd598b8795f3, 7751c8dc-9bf6-4a21-9ea5-376f2be83913, 373fd690-4171-4503-ab1b-d622c3ec6fc7], srvNodes=[TcpDiscoveryNode [id=7751c8dc-9bf6-4a21-9ea5-376f2be83913, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9460], discPort=9460, order=1, intOrder=1, lastExchangeTime=1496754273954, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], TcpDiscoveryNode [id=bf7a4e48-4867-437b-9cc5-dd598b8795f3, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9461], discPort=9461, order=6, intOrder=4, lastExchangeTime=1496754273954, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], TcpDiscoveryNode [id=373fd690-4171-4503-ab1b-d622c3ec6fc7, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9462], discPort=9462, order=7, intOrder=5, lastExchangeTime=1496754273954, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], TcpDiscoveryNode [id=fa2d0f11-80cf-4891-9533-7a36392157f6, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:9463], discPort=9463, order=8, intOrder=6, lastExchangeTime=1496754516085, loc=true, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false]], super=GridFutureAdapter [ignoreInterrupts=false, state=INIT, res=null, hash=1079801970]]] WARN 16:08:36.499 [exchange-worker-#37%svip%] org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager: Failed to wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=8, minorTopVer=0], node=fa2d0f11-80cf-4891-9533-7a36392157f6]. Dumping pending objects that might be the cause:
What can it be? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p13414.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
