ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject RE: Data lost when using write-behind
Date Tue, 19 Apr 2016 20:56:14 GMT

The EVT_NODE_FAILED is fired when any node fails and leaves topology, but
you still don't know which entries are lost because you lost the
write-behind queue that was on that node.

Currently the only way to fully guarantee consistency between cache and DB
is using write-through. After [1] is fixed, this will be also possible with
write-behind in ATOMIC caches. But in TRANSACTIONAL caches write-behind
store makes all DB updates separately, losing the transactional semantics on
DB level, so inconsistencies will still be possible.

[1] https://issues.apache.org/jira/browse/IGNITE-1897


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-lost-when-using-write-behind-tp4265p4342.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message