[
https://issues.apache.org/jira/browse/IGNITE-29106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-29106:
------------------------------------
Description:
When the link between data centers drops in the middle of a commit, a
transaction must not hang and a write the client was told is committed must not
be lost. Nothing tests this.
This adds a JUnit test that holds each message a commit actually sends (lock,
prepare, finish; one- and two-phase; FULL_SYNC and PRIMARY_SYNC; optimistic and
pessimistic), splits the DCs, and checks the outcome before and after the link
is back. If a case loses an acknowledged write, it is filed as an issue with
this reproducer and disabled with a link. Test code only.
was:When the link between data centers drops in the middle of a commit, a
transaction must not hang and a write the client was told is committed must not
be lost. Nothing tests this. This adds a JUnit test that holds each message a
commit actually sends (lock, prepare, finish; one- and two-phase; FULL_SYNC and
PRIMARY_SYNC; optimistic and pessimistic), splits the DCs, and checks the
outcome before and after the link is back. If a case loses an acknowledged
write, it is filed as an issue with this reproducer and disabled with a link.
Test code only.
> Test transactions interrupted by a multi-DC split at every commit message
> -------------------------------------------------------------------------
>
> Key: IGNITE-29106
> URL: https://issues.apache.org/jira/browse/IGNITE-29106
> Project: Ignite
> Issue Type: Test
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Minor
> Labels: IEP-140
>
> When the link between data centers drops in the middle of a commit, a
> transaction must not hang and a write the client was told is committed must
> not be lost. Nothing tests this.
> This adds a JUnit test that holds each message a commit actually sends (lock,
> prepare, finish; one- and two-phase; FULL_SYNC and PRIMARY_SYNC; optimistic
> and pessimistic), splits the DCs, and checks the outcome before and after the
> link is back. If a case loses an acknowledged write, it is filed as an issue
> with this reproducer and disabled with a link. Test code only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
