You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Prasad Bhalerao <pr...@gmail.com> on 2018/02/15 02:19:45 UTC
100% Consistency
Hi,
As per the doc ignite is a s strong or 100% consistent system.
e.g. I have partitioned cache, backup count is 1, and there are two nodes
in cluster.
If I update an entry in cache on one node and before updating the value in
backup cache(update to back is sync or async) the node crashes.
In this scenario the other node becomes primary for the backup data. Now in
this case if I access the cache for the same data for which the update to
backup was failed, will I get the stale data ?
Thanks,
Prasad
Re: 100% Consistency
Posted by Alexey Kukushkin <ku...@gmail.com>.
It is fully consistent only in "full sync" backup update mode but not in
"primary sync" or "async" modes. Relaxing consistency requirements would
give you better performance. Consider if your app really needs full
consistency and configure the backup update mode correspondingly.