-
Hello, I have to deploy an infinispan cluster and I'm doing some tests to compare a replicated vs a distributed setup but I have some troubles understanding how a distributed cache is managed.
which seems legit to me, but if I shutdown all nodes but one, I get
and the remaining node is able to write on the cache. What happens if the link between the nodes is down (but each instance still lives and there are writes on it for the same key), and then goes back up ? Something like an inner timestamp so when the nodes see each other again, the most recent value for a given key is propagated ? Thanks in advance :) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The In regards to why it didn't change, the stats are only updated every 3 seconds by default, maybe it had not yet been updated? The required minimum should be 1 when the number of owners is >= number of nodes. Although this also is assuming you aren't using eviction which can also cause you to need additional nodes to ensure data is not lost. In regards to quorum, the stat |
Beta Was this translation helpful? Give feedback.
-
That was juste a wrong copy/paste, it was indeed set to 1 when the nodes were shutdown.
Yup, that it was a 4 nodes cluster.
Exactly what I was looking for, thanks ! |
Beta Was this translation helpful? Give feedback.
The
required_minimum_number_of_nodes
is just telling you how many nodes you need to keep up to not lose any data. Did you by chance have a cluster of 4 nodes before? If so that is the only way I can see that you had to maintain a minimum of 2 nodes.In regards to why it didn't change, the stats are only updated every 3 seconds by default, maybe it had not yet been updated? The required minimum should be 1 when the number of owners is >= number of nodes. Although this also is assuming you aren't using eviction which can also cause you to need additional nodes to ensure data is not lost.
In regards to quorum, the stat
required_minimum_number_of_nodes
has nothing to do with that as it just i…