Add support for MVCC (TRANSACTIONAL_SNAPSHOT) cache mode.
Risks and Assumptions
In-memory eviction policy can be configured in such a way that will lead to OOM when using batch writing to data pages, so in some degenerate cases the batch writing must be disabled.
For BPlusTree batch operations, ordered keys are required, moreover, an attempt to simultaneously lock the same keys in a different order lead to a deadlock, so batch insertion into the page memory must be performed on an unlocked entries. Alternatively, keys passed in batches from different components (preloader, datastreamer, putAll) should be locked in the same order.
project = Ignite AND labels IN (iep-32) order by key
serverId
5aa69414-a9e9-3523-82ec-879b028fb15b
The improvement in rebalancing time when using batch insertion is mostly noticeable when writing small objects and decreases with increasing object size.the improvement in total rebalancing time is reduced in cases of demander idle waiting for the next messages from the supplier