[
https://issues.apache.org/jira/browse/IGNITE-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20773:
-------------------------------------
Description:
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.
was:
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) thus it's required also to add some integration tests here for the
whole chain.
> 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
>
> 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)
