endet: Dienstag, 13. September 2016 21:00
An: user@ignite.apache.org
Betreff: Re: Write Behind data safety guarantees II
Hi,
In current implementation write-behind store can lose writes even if only one
nodes fails. This can be improved by adding backup queues [1], but it's not
implemented yet.
also lost).
Only synchronous write-through can guarantee that there are no data loss.
[1] https://issues.apache.org/jira/browse/IGNITE-1897
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Write-Behind-data-safety-guarantees-II-tp7696p7721.html
Sent fro
You can have also the case both nodes crash ... The bottom line is that a write
loss can occur in any system. I am always surprised to hear even senior
consultants saying that in a high reliability database no write loss can occur
or the risk is low (think about the human factor! Eg an admin acc
Hi,
I've been trying to find information on cache persistence write behind behavior
that might lead to entries not being written to the persistent store. Most
notably: what happens in the following scenario:
* Cache 'cache' has two backup copies on nodes A and B respectively and
is c
