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

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/05/17 13:21:00 UTC

[jira] [Created] (IGNITE-19508) Design and breakdown tx on unstable topology topic.

Alexander Lapin created IGNITE-19508:
----------------------------------------

             Summary: Design and breakdown tx on unstable topology topic.
                 Key: IGNITE-19508
                 URL: https://issues.apache.org/jira/browse/IGNITE-19508
             Project: Ignite
          Issue Type: Task
            Reporter: Alexander Lapin


h3. Motivation

General approach of tx recovery/tx on unstable topology is available in described in [https://cwiki.apache.org/confluence/display/IGNITE/IEP-91%3A+Transaction+protocol#IEP91:Transactionprotocol-Recovery|IEP-91]

Thus it's required to prepare full set of tickets in order to handle
 * Data node (primaryReplica|majority) failure.
 * Commit partition failure.
 * Tx coordinator failure.

except disaster recovery and graceful primary replica switch, that will be covered in separate topics.
h3. Definition of Done
 * Corresponding epic is created.
 * Epic is populated with full set of tasks.
 * Tasks are estimated and assigned to sprints.



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