[
https://issues.apache.org/jira/browse/IGNITE-16096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-16096:
---------------------------------------
Description:
We need to implement MVCC support to avoid locking.
Generally, the idea is to use monotonic timestamps to globally order the
transactions.
See [1][2] for decentralized timestamp generation techniques:
[1]
[http://users.ece.utexas.edu/~garg/pdslab/david/hybrid-time-tech-report-01.pdf]
[2] [https://www.usenix.org/system/files/nsdi21-wei.pdf]
was:
We need to implement MVCC support to avoid locking.
Generally, the idea is to use monotonic timestamps to globally order the
transactions.
See [1][2] for timestamp generation techniques:
[1]
[http://users.ece.utexas.edu/~garg/pdslab/david/hybrid-time-tech-report-01.pdf]
[2] https://www.usenix.org/system/files/nsdi21-wei.pdf
> Implement MVCC support to avoid excessive locking
> -------------------------------------------------
>
> Key: IGNITE-16096
> URL: https://issues.apache.org/jira/browse/IGNITE-16096
> Project: Ignite
> Issue Type: Task
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: iep-61, ignite-3
>
> We need to implement MVCC support to avoid locking.
> Generally, the idea is to use monotonic timestamps to globally order the
> transactions.
> See [1][2] for decentralized timestamp generation techniques:
> [1]
> [http://users.ece.utexas.edu/~garg/pdslab/david/hybrid-time-tech-report-01.pdf]
> [2] [https://www.usenix.org/system/files/nsdi21-wei.pdf]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
