When testing the write-behind feature, I found the data which would be persisted to back-end database was put in a queue of JVM. That means if that server crash, the data which has not been persisted to the database will be lost. Even though that part of data can be found in other server's memory, that data can not be updated to database automatically. So I want to make clear what the recommended scenario is to use write-behind and how to handle the server crash when using write-behind.
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-lost-when-using-write-behind-tp4265.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
