Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-16331

[Extensions] Add implementation of pluggable topology validator.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • extensions
    • Docs Required, Release Notes Required

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              PetrovMikhail Mikhail Petrov
              PetrovMikhail Mikhail Petrov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: