Re: Restore data from Ignite snapshots

2022-02-03 Thread Maxim Muzafarov
Hello, You don't need to stop the cluster or delete/move any snapshot files in case you are using the restore procedure from the control.sh, so the following should work: - create snapshot - stop the caches you are intended to restore - run ./control.sh --snapshot restore snapshot_1 --start Can y

Re: Restore data from Ignite snapshots

2022-02-03 Thread Surinder Mehra
Hi, So the way I am thinking to use it is if we lose the EBS volume and we need to restore the cluster state back. I would have a secondary EBS as my snapshot directory so I can restore from it. It means Application would need to be restarted after EBS data is copied back to the work directory. I s

Re: Server cache reads less number of entries than number of entries put by client cache

2022-02-03 Thread Sumit Deshinge
Yes, that I am sure, because the keys are generated using ignite uuid, which internally is based on hostname, and all the clients are hosted on machines with unique hostnames. On Wed, Feb 2, 2022 at 3:23 PM Pavel Tupitsyn wrote: > Are you sure that all entry keys are unique? > E.g. if you do 500

Too many open cursors issue after cache partition loss exceptions

2022-02-03 Thread Sumit Deshinge
Hi, I am adding a large amount of data into ignite cache using multiple thin clients hosted on different machines. Ignite cache configuration is FULL_SYNC with REPLICATED mode. After few hours of data addition, I can see multiple below exceptions: org.apache.ignite.internal.processors.cache.Cache

Re: Server cache reads less number of entries than number of entries put by client cache

2022-02-03 Thread Pavel Tupitsyn
So we have the following situation: * Put 5000 unique keys with putAll * Use cache iterator, observe less than 5000 keys Is that correct? On Thu, Feb 3, 2022 at 7:53 PM Sumit Deshinge wrote: > Yes, that I am sure, because the keys are generated using ignite uuid, > which internally is based on

OOME on startup with 2.11.1 and 2.12

2022-02-03 Thread Sachin1.Garg
We are planning to upgrade from 2.9 to 2.11.1. But as soon as we start the 2.11.1 or 2.12 ignite instance crashes with OOME error. [20:15:05,474][SEVERE][grid-nio-worker-client-listener-2-#34][] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHa

Re: Server cache reads less number of entries than number of entries put by client cache

2022-02-03 Thread Sumit Deshinge
That's correct, but this is when we use Pessimistic + Repeatable_Read transaction at Server side where we are using an iterator to read, remove and insert into new cache in the transaction. And this issue is not observed every time, but intermittently. And note that, if I don't use transactions or

Re: Server cache reads less number of entries than number of entries put by client cache

2022-02-03 Thread Pavel Tupitsyn
Can you please share the code? On Fri, Feb 4, 2022 at 8:36 AM Sumit Deshinge wrote: > That's correct, but this is when we use Pessimistic + Repeatable_Read > transaction at Server side where we are using an iterator to read, remove > and insert into new cache in the transaction. And this issue i

Re: OOME on startup with 2.11.1 and 2.12

2022-02-03 Thread Zhenya Stanilovsky
hello, seems you really use all available memory, of course without heap dump i have no clue why it`s happen, plz increase -Xmx and check once more.   >  >We are planning to upgrade from 2.9 to 2.11.1. But as soon as we start the >2.11.1 or 2.12 ignite instance crashes with OOME error. >  >[20

Re: OOME on startup with 2.11.1 and 2.12

2022-02-03 Thread Zhenya Stanilovsky
also seems you open a lot of jdbc connections or some configurations issue …  attach your config and give more info about startup ? num of servers ? who and how was connected to grid ?   >  >We are planning to upgrade from 2.9 to 2.11.1. But as soon as we start the >2.11.1 or 2.12 ignite inst