To be honest, I'm not sure I understand the problem. In case of write-behind, Ignite will try to save as much entries as possible in case connection to DB is lost. It will basically keep entries in queue until the queue is too large, and then will start to evict from it to avoid OOME. Once connection is restored, it should start flushing entries that are still in queue to the DB. Do you observe another behavior?
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/When-writethrough-processing-Persistent-storage-failed-tp8622p8742.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
