[
https://issues.apache.org/jira/browse/IGNITE-27697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-27697:
---------------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
Release Note: Disabled table (hierarchy) locks on transaction path
> Get rid of table locks
> ----------------------
>
> Key: IGNITE-27697
> URL: https://issues.apache.org/jira/browse/IGNITE-27697
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 3.1
> Reporter: Alexey Scherbakov
> Assignee: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> IGNITE-20895 mentions the possibility of removing table(hierarchy) locks.
> At this point of time they still got no use in code, except to ensure tx
> isolation in case of full table scans, using the combination of S and IX
> locks.
> This can be replaced with primary key index scans.
> Other possible use for table locks is efficient implementation of exclusive
> table locks, but instead this should be implemented using schema sync
> approach.
> I propose to disable table locks to remove additional overhead on hot path
> and improving concurrency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
