You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2022/09/20 21:28:00 UTC

[jira] [Assigned] (IGNITE-17732) Avoid locking indexes in transaction

     [ https://issues.apache.org/jira/browse/IGNITE-17732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladislav Pyatkov reassigned IGNITE-17732:
------------------------------------------

    Assignee: Vladislav Pyatkov

> Avoid locking indexes in transaction
> ------------------------------------
>
>                 Key: IGNITE-17732
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17732
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>
> The transaction protocol requires lock all indexes (now it is a pk) in the same manner as it happens for data (locks on {_}RowIds{_}). But lock manager cannot resolve all problems in his case (in particular, waiter for _RowId_ does not create when the lock on index have not got).
> As a temporary workaround for this disadvantage, supposed:
>  # Create a NAL (Not a lock) lock mode, which is compatible for all another mode
>  # All lock modes on PK should convert to NAL 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)