Client node disconnected from cluster

Getting below error on ignite server: FAIL: [tcp-disco-client-message-worker-[[CredentialsTcpDiscoverySpi] Client node considered as unreachable and will be dropped from cluster, because no metrics update messages received in interval: TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be

Ignite cluster issue

My application is running with two nodes and two nodes are in one cluster. all the cache ids are available. All of sudden yesterday, two clusters are created and one node for each. now we got problem. Could you please help me, all of sudden why cluster is created automatically? how clusters are

Re: ignite partition mode

By using ignite web console -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite partitioned

$ ./control.sh --baseline Control utility [ver. 2.8.0#20200226-sha1:341b01df] 2020 Copyright(C) Apache Software Foundation User: Time: 2020-08-21T09:13:11.334 Command [BASELINE] started Arguments: --baseline

Re: Ignite partitioned

Could you please help with this. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite partitioned

My topology snap shot: [06:46:33,961][INFO][disco-event-worker-#44][GridDiscoveryManager] Topology snapshot [ver=27, locNode=, servers=2, clients=17, state=ACTIVE, CPUs=32, offheap=90.0GB, heap=160.0GB] How should we know, is it formed cluster or not. -- Sent from:

ignite partition mode

Our application running with 2 ignite node,. But data is available in one node, and not available in the second node. Our cache configuration: Cache mode:partitioned Automatic mode:atomic Write Synchronization mode:full_sync Backups:1 Rebalance delay:1 We have above cache configuration.

Ignite partitioned

Our application running with 2 ignite node,. But data is available in one node, and not available in the second node. Our cache configuration: Cache mode:partitioned Automatic mode:atomic Write Synchronization mode:full_sync Backups:1 Rebalance delay:1 We have above cache configuration.

ignite partition mode

Our application running with 2 ignite node,. But data is available in one node, and not available in the second node. Our cache configuration: Cache mode:partitioned Automatic mode:atomic Write Synchronization mode:full_sync Backups:1 Rebalance delay:1 We have above cache configuration.

Cache configuration

My cache ids are dynamic. Is it possible to add cache configuration in xml. I have checked, name property is mandatory. But i cannot add the name as it's dynamic name. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Can not finish proxy initialization in logs

Hi Team, Recently i have upgraded ignite version 2.6 to 2.8 version. I am getting below INFO "Can not finish proxy initialization" 3:19:26.806 [sys-#273] INFO o.a.i.i.p.cache.GridCacheProcessor - Can not finish proxy initialization because proxy does not exist, cacheName=,

Re: ignite web agent issue

Could you please let me know, what is the supported mongodb version. Please let me know the mongodb version, which your using. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite web agent issue

thank you for the help. To Building Ignite Web Agent, shall we need MongoDB (version >=3.2.x <=3.4.15) and NodeJS (version >=8.0.0) ??? Could you please let me know, the stop to building the web agent from source's. As for the docs Building Ignite Web Agent To build Ignite Web Agent from

ignite web agent issue

Hi Team, Currently my application is using ignite 2.6.0 version and ignite web agent version is ignite-web-agent-2.4.4. Everything is working fine. Now we are migrating ignite 2.6.0 to 2.8.0. Ignite 2.8.0 will support the ignite-web-agent-2.4.4?? While running the queries i am getting below