[
https://issues.apache.org/jira/browse/IGNITE-28952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113871#comment-18113871
]
Maksim Davydov commented on IGNITE-28952:
-----------------------------------------
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyleDucktests?branch=pull%2F13576%2Fhead#all-projects
> [ducktests] MDC tests for majority based topology validation
> ------------------------------------------------------------
>
> Key: IGNITE-28952
> URL: https://issues.apache.org/jira/browse/IGNITE-28952
> Project: Ignite
> Issue Type: Task
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Minor
> Labels: IEP-140, ducktests, ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> MdcTopologyValidator has two modes and the number of data centers picks one:
> with
> an EVEN DC count a segment stays writable while it sees the main DC, with an
> ODD
> one while it sees a majority of the DC set. The ducktest fixture only ever
> built a
> two DC cluster, so only the first mode is covered.
> Let MdcCluster span an arbitrary DC set, compile the cache parameters from
> it, and
> cut several cross-DC links apart in one round-trip. On top of that, three
> scenarios
> over three DCs: one DC isolated, a three way split, and a DC lost outright.
> from the two others, parametrized over which DC is isolated; a three way
> split in which
> every segment goes read-only; and data centers lost one by one, writable
> while a majority
> survives and read-only below it. Every partition owns one copy per DC, so
> every segment
> still serves every read - that is what separates the read assertions from
> the write ones.
> - Framework unit checks for the DC-count dependent parts: validator mode
> selection, backup
> arithmetic, the impairment mesh and its per-pair overrides, and the
> per-node command
> compilation of single and multi-link partitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
