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

improve view change at moment of blacklisting

    XMLWordPrintable

Details

    • Task
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • None
    • None

    Description

      This ticket is a follow-up to INDY-193.

      In that ticket's comment stream, spivachuk identified some follow-up work that could be done to make us more robust. Here is what he said:

      "To trigger view change at the moment when the master's primary is blacklisted the first time we need to introduce notifying other nodes about some node is blacklisted and a mechanism of requesting known transactions from other node for verification only. Such the fix seems to be rather time-consuming while the issue seems not to be critical because blacklisting of some node by other nodes one by one during their catch-ups will eventually cause a view change. So I propose to schedule this work for the time after Minimal Go-Live."

      This ticket is to track that work.

      Attachments

        Activity

          People

            Unassigned Unassigned
            danielhardman Daniel Hardman
            Alexander Shcherbakov, Daniel Hardman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: