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

If partition consistency cannot be restored during rebalance using counters the most recent partition data should be used.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Docs Required

    Description

      This is possible if all owners are left, then returned and counters are inconsistent (no dedicated max counter node)

      In such a case the "most recent" partition can be used for supplying purposes.

      We should track topology history to find the node with "most recent" updates.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue IGNITE-17738 Cluster must be able to fix the partition inconsistency on restart/node_join by itself

          • Major - Major loss of function.
          • Resolved
          requires

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-10078 Node failure during concurrent partition updates may cause partition desync between primary and backup.

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              ascherbakov Alexey Scherbakov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: