Hello! I recommend setting clientReconnectDisabled setting to true, and then do your reconnects manually. I have heard of the issue where restarting a client would interfere with data structures.
If you have a reproducer for this problem, I could review it and file a ticket against Apache Ignite JIRA. Regards, -- Ilya Kasnacheev пт, 18 сент. 2020 г. в 02:48, xmw45688 <[email protected]>: > Thanks. > We tried it outside the transaction when the ignite instance restarted with > EventType.EVT_CLIENT_NODE_RECONNECTED. However, it is hang at > igniteInstance.atomicLong(....). > // when the ignite instance restarted, it hangs here > userSeq = igniteInstance.atomicLong("userSeq", maxId, true); > userSeq.getAndSet(maxId); > > We know that the sequence was removed, does the client keep the reference > to > the old Ignite server? How do we clear this reference and reset? Or we > did > it incorrectly. > > Thanks, > Xinmin > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
