ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shaomin Zhang <Shaomin.Zh...@tudor.com>
Subject RE: Data lost when using write-behind
Date Thu, 21 Apr 2016 15:25:19 GMT

In the case of the primary failure, it send out a EVT_NODE_FAILED event, is the CacheStoreSessionListener.onSessionEnd()
method still be called? Which one goes first, the event or the onSessionEnd() method?

Thanks again


-----Original Message-----
From: vkulichenko [mailto:valentin.kulichenko@gmail.com]
Sent: 19 April 2016 21:56
To: user@ignite.apache.org
Subject: RE: Data lost when using write-behind


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.

This email, its contents, and any attachments transmitted with it are intended only for the
addressee(s) and may be confidential and legally privileged. We do not waive any confidentiality
by misdelivery. If you have received this email in error, please notify the sender immediately
and delete it. You should not copy it, forward it or otherwise use the contents, attachments
or information in any way. Any liability for viruses is excluded to the fullest extent permitted
by law.

Tudor Capital Europe LLP (TCE) is authorised and regulated by The Financial Conduct Authority
(the FCA). TCE is registered as a limited liability partnership in England and Wales No: OC340673
with its registered office at 10 New Burlington Street, London, W1S 3BE, United Kingdom

View raw message