persistent caches not rebalancing when new node is added

I have a 16 node Ignite (v2.10.0) cluster with persistence enabled, and about 20 caches, all of which are configured as cacheMode = partitioned, backups = 1, with a rebalanceMode of ASYNC and rebalanceDelay of -1 (such that rebalancing will only happen manually). The auto baseline adjustment featur

data rebalancing and partition map exchange with persistence

I'm using Ignite 2.9.1, a 5 node cluster with persistence enabled, partitioned caches with 1 backup. I'm a bit confused about the difference between data rebalancing and partition map exchange in this context. 1. Does data rebalancing occur when a node leaves or joins, or only when you manually c

ClassNotFoundException using peer class loading on cluster

I'm using peer class loading on a 5 node ignite cluster, persistence enabled, Ignite version 2.8.1. I have a custom class that implements IgniteRunnable and I launch that class on the cluster. This works fine when deploying to an ignite node running on a single node cluster locally, but fails with

Re: IgniteCache.size() is hanging

Sorry, meant 2.7.6, not 2.7.3 On Tue, Sep 29, 2020 at 7:40 AM Alan Ward wrote: > I wish I could -- this cluster is running on an isolated network and I > can't get the logs or configs or anything down to the Internet. > > But, I just figured out the problem -- I had set a ver

Re: IgniteCache.size() is hanging

other > information in the logs. Can you provide them? > > BR, > Andrei > 9/24/2020 6:54 PM, Alan Ward пишет: > > The only log I see is from one of the server nodes, which is spewing at a > very high rate: > > [grid-nio-worker-tcp-comm-...][TcpCommunicationSpi] Accepted

Re: IgniteCache.size() is hanging

The only log I see is from one of the server nodes, which is spewing at a very high rate: [grid-nio-worker-tcp-comm-...][TcpCommunicationSpi] Accepted incoming communication connection [locAddr=/:47100, rmtAddr=: Note that each time the log is printed, i see a different value for . Also note th

IgniteCache.size() is hanging

[image: Selected post] I'm running a 5 node Ignite cluster, version 2.8.1, with persistence enabled and a small number of partitioned caches, ranging between a few thousand records to one cache with over 1 billion records. No SQL use. When I run a Java client app and connect to the cluster (with c

Ignoring model fields

Is there a way (preferably annotation-based) to exclude certain fields in user-defined model classes from Ignite (cache, query, etc.), similar to how Jackson has a @JsonIgnore annotation to exclude a field from serialization/deserialization. Thanks, Alan

local deployment of web-console-standalone

I'm trying to get a local deployment of the web console working via docker. I have the latest 2.7.0 version of the web-console-standalone docker image, started with "docker run -d -p 8080:80 --name web-console-standalone -e DEBUG=* apacheignite/web-console-standalone The container starts up fine,