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 2023/11/28 16:37:00 UTC

[jira] [Commented] (IGNITE-20773) Adjust lock resolution procedure in order to have an ability to do tx coordinator liveness check

    [ https://issues.apache.org/jira/browse/IGNITE-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790647#comment-17790647 ] 

Vladislav Pyatkov commented on IGNITE-20773:
--------------------------------------------

Merged 81949957cbfffe397f979ef5f9c9a72842204a03

> Adjust lock resolution procedure in order to have an ability to do tx coordinator liveness check
> ------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-20773
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20773
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> h3. Motivation
> In order to implemented liveness check and thus initiate transaction recovery if the corresponding coordinator is dead, it's required to adjust lock resolution procedure.
> h3. Definition of done
> Liveness check described in IGNITE-20771 is triggered, meaning that txId of first lock is available.
> h3. Implementation Notes
> Given ticket finishes the chain of lock triggered tx recovery (coordinator aspect) besides tests that will be covered separately.



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