ignite 2.8.1: Failed to resolve node topology

Hi, We have a crash in our environment with the below error. Any insight into what might have gone wrong? regards Mahesh ^-- Heap [used=17211MB, free=64.98%, comm=49152MB] ^-- Off-heap [used=48448MB, free=26.41%, comm=65736MB] ^-- sysMemPlc region [used=0MB, free=99.98%, comm=100MB]

Re: How to do address resolution?

Not sure if this will help, I've also had issues with Visor keeps hanging the cluster. When I changed the configuration to ClientMode (default is ServerMode) it solved my problem. Might be good to give it a try. Humphrey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How do I know the cache rebalance is finished?

Rebouncing this topic, the ticket is still open (almost 4 years). Any progress / priority to this ticket or work around? https://issues.apache.org/jira/browse/IGNITE-3362. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite node top ram limit

Is there a RAM limit for single node (hardcoded or practical)? What practical top limit is comfortable in terms of node failures?

Re: Ignite Backup and Restore

Hi, any suggestions? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: [External]Re: Ignite cluster became unresponsive

Hi Stephen/Team, Did you got any chance to look into this? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 06 July 2020 14:50 To: user@ignite.apache.org Subject: RE: [External]Re: Ignite cluster became unresponsive Hi Stephen, We have started our node with below JVM parameters. Als

Re: What does all partition owners have left the grid on the client side mean?

Yeah I restarted the server nodes. But I guess the client didn't reconnect Hum On Tue., Jul. 7, 2020, 5:52 p.m. Evgenii Zhuravlev, < e.zhuravlev...@gmail.com> wrote: > John, > > Unfortunately, I didn't find messages about lost partitions for this > cache, there is a chance that it hap