Re: Ignite client node hangs while IgniteAtomicLong is created

Hello Ilya, I have a look at your logs and thread dumps. This definitely a bug. The data structure processor does not properly initialize when a client node connects to a cluster that changes its own state (state transition from the inactive state to active). I have created a ticket in order to

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello, Ilya, In the post above one week ago I've attached necessary thread dumps. Could you please say whether do you have sufficient information to investigate the problem with hanging of IgniteAtomicLong? I think the issue not all that harmless, it concerns the last Ignite 2.8.1 and its fixing

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello, Ilya,Attached are two thread dumps, the second is taken 13 minutes after thefirst one: threaddump.txt , threaddump2.txt .The hanging

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello, Ilya, Attached are two thread dumps, the second is taken 13 minutes after the first one: threaddump.txt , threaddump2.txt . The

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello! Can you collect thread dumps from all nodes once you get them hanging? Can you throw together a reproducer project? Regards, -- Ilya Kasnacheev вт, 4 авг. 2020 г. в 12:51, Ilya Roublev : > We are developing Jira cloud app using Apache Ignite both as data storage > and as job

Ignite client node hangs while IgniteAtomicLong is created

We are developing Jira cloud app using Apache Ignite both as data storage and as job scheduler. This is done via a standard Ignite client node. But we need to use Atlassian Connect Spring Boot to be able to communicate with Jira. In short, all is done exactly as in our article Boosting Jira Cloud