> 2 servers and 1 client, and no backups > shut down one node There are no backups => any node shutdown leads to partition loss. If you want to ignore data loss, set partitionLossPolicy = IGNORE [1]
[1] https://ignite.apache.org/docs/latest/configuring-caches/partition-loss-policy On Wed, Sep 18, 2024 at 12:04 PM <[email protected]> wrote: > Hi. > > > > We are using Apache Ignite in our application, and currently, we are > testing the behaviour of the system when there are system errors. > > > > One of our tests is not working as expected: > > - we have got an Ignite cluster with 2 servers and 1 client, and no > backups > - Ignite version 2.16 > - We shut down one node server for several minutes > - During this time there is no read nor write to Ignite (we do not use > the DB) > - When we restart the server node, we expect to recover the system > smoothly BUT we have exceptions when we query the data: “Failed to execute > query because cache partition has been lost” > > > > We can resolve the problem resetting the lost partitions, but is this a > normal behaviour of Ignite? I mean, it is a simple case, and the node > should be able to join the cluster without problems. > > > > Thank you. > > >
