[
https://issues.apache.org/jira/browse/IGNITE-28450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-28450:
---------------------------------------
Description:
Certain KV operations, like RW_UPSERT, RW_UPSERT_ALL etc, acquire S index locks
in resolveRowByPk.
Later this lock is upgraded to X.
Under contention such upgrade can produce large number of lock conflicts.
Instead, index locks should be locked with X from the beginning.
was:
Certain KV operations, like RW_UPSERT, RW_UPSERT_ALL etc, acquire S index locks
in
resolveRowByPk.
Later this lock is upgraded to X.
Under contention such upgrade can produce large number of lock conflicts.
Instead, index locks should be locked with X from the beginning.
> Reduce lock conflict probability for certain KV operations
> ----------------------------------------------------------
>
> Key: IGNITE-28450
> URL: https://issues.apache.org/jira/browse/IGNITE-28450
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> Certain KV operations, like RW_UPSERT, RW_UPSERT_ALL etc, acquire S index
> locks in resolveRowByPk.
> Later this lock is upgraded to X.
> Under contention such upgrade can produce large number of lock conflicts.
> Instead, index locks should be locked with X from the beginning.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
