Hi Evgenii, What's more interesting If we reboot them in very shut time like one hour, from our monitor log we can find
such like NODE_LEFT and NODE_JOIN events, every thing move smoothly . But if after several hours, problem below sure will happen if you try to reboot any node from cluster. Regards Aaron Aaron.Kuai From: aa...@tophold.com Date: 2018-01-17 20:05 To: user Subject: Re: Re: Nodes can not join the cluster after reboot hi Evgenii, Thanks! We collect some logs, one is the server which is reboot, another two are two servers exist, one client only nodes. after reboot: 1. the reboot node never be totally brought up, waiting for ever. 2. other server nodes after get notification the reboot node down, soon hang up there also. 3. the pure client node, only call a remote service on the reboot node, also hang up there At around 2018-01-17 10:54 we reboot the node. From the log we can find: [WARN ] 2018-01-17 10:54:43.277 [sys-#471] [ig] ExchangeDiscoveryEvents - All server nodes for the following caches have left the cluster: 'PortfolioCommandService_SVC_CO_DUM_CACHE', 'PortfolioSnapshotGenericDomainEventEntry', 'PortfolioGenericDomainEventEntry' Soon a ERROR log(Seem the only ERROR level log): [ERROR] 2018-01-17 10:54:43.280 [srvc-deploy-#143] [ig] GridServiceProcessor - Error when executing service: null java.lang.IllegalStateException: Getting affinity for topology version earlier than affinity is calculated Then a lot WARN of "Failed to wait for partition release future........................." Then this forever loop there, from the diagnose nothing seem suspicious, All node eventually output very similar. [WARN ] 2018-01-17 10:55:19.608 [exchange-worker-#97] [ig] diagnostic - Pending explicit locks: [WARN ] 2018-01-17 10:55:19.609 [exchange-worker-#97] [ig] diagnostic - Pending cache futures: [WARN ] 2018-01-17 10:55:19.609 [exchange-worker-#97] [ig] diagnostic - Pending atomic cache futures: [WARN ] 2018-01-17 10:55:19.609 [exchange-worker-#97] [ig] diagnostic - Pending data streamer futures: [WARN ] 2018-01-17 10:55:19.609 [exchange-worker-#97] [ig] diagnostic - Pending transaction deadlock detection futures: Some of our environment: 1. we open the peer class loading flag, but in fact we use fat jar every class is shared. 2. some nodes deploy service, we use them as RPC way. 3. most cache in fact is LOCAL, only when must we make them shared 4. use JDBC to persist important caches 5. TcpDiscoveryJdbcIpFinder as the finder All others configuration is according to the stand. Thanks for your time! Regards Aaron Aaron.Kuai From: Evgenii Zhuravlev Date: 2018-01-16 20:32 To: user Subject: Re: Nodes can not join the cluster after reboot Hi, Most possible that on the of the nodes you have hanged transaction/future/lock or even a deadlock, that's why new nodes can't join cluster - they can't perform exchange due to pending operation. Please share full logs from all nodes with thread dumps, it will help to find a root cause. Evgenii 2018-01-16 5:35 GMT+03:00 aa...@tophold.com <aa...@tophold.com>: Hi All, We have a ignite cluster running about 20+ nodes, for any case JVM memory issue we schedule reboot those nodes at middle night. but in order to keep the service supplied, we reboot them one by one like A,B,C,D nodes we reboot them at 5 mins delay; but if we doing so, the reboot nodes can never join to the cluster again. Eventually the entire cluster can not work any more forever waiting for joining to the topology; we need to kill all and reboot from started, this sound incredible. I not sure whether any more meet this issue before, or any mistake we may make, attached is the ignite log. Thanks for your time! Regards Aaron Aaron.Kuai
