You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Davydov (Jira)" <ji...@apache.org> on 2026/10/02 14:50:00 UTC

[jira] [Created] (IGNITE-29101) Cover multi-DC main DC loss, majority loss and coordinator change with JUnit tests, and check the validator's DC set

Maksim Davydov created IGNITE-29101:
---------------------------------------

             Summary: Cover multi-DC main DC loss, majority loss and coordinator change with JUnit tests, and check the validator's DC set
                 Key: IGNITE-29101
                 URL: https://issues.apache.org/jira/browse/IGNITE-29101
             Project: Ignite
          Issue Type: Test
            Reporter: Maksim Davydov
            Assignee: Maksim Davydov


Several multi-DC ducktests check behavior that doesn't depend on a real network: losing and regaining the main DC, reading after the majority is lost, and that the oldest server becomes coordinator (a guard; coordinator choice doesn't depend on DCs). Each takes minutes in Docker and runs rarely. This moves those checks into JUnit tests that run before every merge, and adds two disabled checks, each linked to its issue: majority mode counting data centers outside its configured set, and an even set of data centers without a main one being accepted. Test code only.



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