Re: ignite-persistence distribution is not even

2021-11-09 Thread Stephen Darlington
Ignite exports lots of other metrics: https://ignite.apache.org/docs/latest/monitoring-metrics/intro You need to look at the number of pages used and the fill rate (how full each page is on average) to figure out how much space you’re actually using. > On 9 Nov 2021, at 11:22, Ibrahim Altun wr

Re: ignite-persistence distribution is not even

2021-11-09 Thread Ibrahim Altun
Looking at the size of the persistence files isn’t necessarily a good metric, as Ilya notes. -> but still files physically occupy disk space, in this case i don't know if i need to increase disk space or not. On Tue, 9 Nov 2021 at 14:17, Stephen Darlington < stephen.darling...@gridgain.com> wrote:

Re: ignite-persistence distribution is not even

2021-11-09 Thread Stephen Darlington
It shows how the data is distributed. Looking at the size of the persistence files isn’t necessarily a good metric, as Ilya notes. > On 9 Nov 2021, at 10:21, Ibrahim Altun wrote: > > @ilya We did not force system to remove any keys, just add a new node to the > cluster, so my expectation was

Re: ignite-persistence distribution is not even

2021-11-09 Thread Ibrahim Altun
@ilya We did not force system to remove any keys, just add a new node to the cluster, so my expectation was system to distribute ~120GB data across the nodes, and expect to see ~80GB of data on each node (have total ~60GB(without backup size) primary data, divided into 3 nodes ~40GB primary ~40GB b

Re: ignite-persistence distribution is not even

2021-11-09 Thread Stephen Darlington
You can check the distribution with the control script: ./control.sh —cache distribution null This displays the number of records per partition for all caches and nodes. > On 8 Nov 2021, at 20:24, Shishkov Ilya wrote: > > Hi! > As I know, if you remove some cache entries (keys), their corresp

Re: ignite-persistence distribution is not even

2021-11-08 Thread Shishkov Ilya
Hi! As I know, if you remove some cache entries (keys), their corresponding segments in the data pages remain empty in the persistent store until you insert these keys back into Ignite. So, it looks like voids in data pages. But the rebalanced data is put into persistent storage without any kind of

ignite-persistence distribution is not even

2021-11-08 Thread Ibrahim Altun
Hi, We had a 2 node cluster with persistence enabled with backup(1) enabled, this morning we've added a new node to the cluster. Although rebalancing is finished Ignite Persistence values are not evenly distributed; server-1: [2021-11-08T14:31:29,371][INFO ][grid-timeout-worker-#13][IgniteKernal