[jira] [Updated] (IGNITE-15932) Implement storage for locks

[Alexander Lapin (Jira)]

Title: Message Title

Alexander Lapin updated an issue   Ignite / IGNITE-15932 Implement storage for locks Change By: Alexander Lapin Currently locks are stored in the heap and can take unlimited amount of memory. Need to implement storage for a locks with a configurable limits. It can even store locks off-heap of use disk spilling. Lock attempt must fail if a storage is overflowed. *Upd:* It's required to introduce both volatile and persistent storages for locks. Volatile storages will be used directly  from replica, persistent ones will be populated from within corresponding ParitionListeners. Volatile storage will manager both read and write locks for all types of lock entities: rowIds, index keys, tables, indexes, meaning that it covers both common and intent locks. It's an open question whether persistent storage should handle (and replicate intent locks), so for now it will only handle common write locks. Please pay attention that persistent storage should be fully integrated into raft replication logic: snapshots, [ checkpointIndexes |https://issues.apache.org/jira/browse/IGNITE-16907] , etc. To sum up, persistent storage isn't a part of transactions3_rw stable support, however it's better to implement it from the very begging. Add Comment   This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)