Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1759

Use persisted last_pp_seq_no for recovery of backup primaries

    Details

    • Type: Task
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.6.79
    • Component/s: None
    • Labels:
      None

      Description

      As of now, if master primary crashed (stopped) and re-started, it will get last_pp_seq_no from other Nodes and continue correct ordering.

      For backup primaries this information is not propagated, so backup primary will start sending PRE-PREPARES from 1, and other nodes will reject it. It may eventually cause a memory leak, since ordering on this backup is stopped for some time.

      Acceptance criteria

      • Create a new key-value DB for persisting current states
      • Persist last pp_seq_no for each Instance in the pool
      • Use persisted last_pp_seq_no as a new pp_seq_no for a Replica if it's a primary in one of the Instances (including Master?)

        Attachments

        1. 1759.tar.gz
          545 kB
        2. INDY-1759_ok_1.PNG
          INDY-1759_ok_1.PNG
          315 kB
        3. INDY-1759_ok_2.PNG
          INDY-1759_ok_2.PNG
          313 kB
        4. INDY-1759_ok_primaries.PNG
          INDY-1759_ok_primaries.PNG
          97 kB
        5. INDY-1759.PNG
          INDY-1759.PNG
          242 kB

          Issue Links

            Activity

              People

              • Assignee:
                VladimirWork Vladimir Shishkin
                Reporter:
                ashcherbakov Alexander Shcherbakov
                Watchers:
                Alexander Shcherbakov, Artem Obruchnikov, Nikita Spivachuk, Vladimir Shishkin
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: