[
https://issues.apache.org/jira/browse/IGNITE-16331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-16331:
-------------------------------------
Fix Version/s: 2.13
> [Extensions] Add implementation of pluggable topology validator.
> ----------------------------------------------------------------
>
> Key: IGNITE-16331
> URL: https://issues.apache.org/jira/browse/IGNITE-16331
> Project: Ignite
> Issue Type: Improvement
> Components: extensions
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Fix For: 2.13
>
>
> It is needed to add an implementation of the Ignite plugin to solve the
> problem of data inconsistency in case of a cluster split into several
> independent parts due to network problems.
> This problem can be solved by providing the guarantee that
> after cluster segmentation, no more than one segment can process write
> requests to all caches.
> It is proposed to
> 1. reuse Ignite topology validation mechanism to block cache writes
> 2. automatically apply topology validation logic for all caches through
> CacheTopologyValidatorProvider
> 3. rely on remaining Ignite baseline nodes in the topology to determine
> what segment can continue to process write requests, if any
> 4. automatically switch state of the segment to READ-ONLY if it is considered
> as write blocked
> 5. change segment state to ACTIVE mode to automatically restore write
> availability to all caches
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
