Hi, You're right, write-behind store has a back pressure mechanism that starts to update DB synchronously if the queue is too long. Otherwise you will most likely eventually get out of memory error.
The backlog size is controlled by CacheConfiguration.setWriteBehindFlushSize() property. When this size is reached, the store will start flushing to the database in the background. If it will detect that the flushing process is slower than cache updates (i.e., the backlog continuous growing above the setting), it will switch to sync updates. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Inserts-stalled-by-write-behind-process-tp3390p3399.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
