Stop mutating old topology on set version/election id updates

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.7.0.rc0
    • Affects Version/s: None
    • Component/s: Spec Comp
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This code in cluster is problematic:

                  topology.update_max_election_id(description)
                  topology.update_max_set_version(description)
      

      ... since it mutates the previous topology. Figure out where to put the logic in those methods so that it can be invoked without mutating the old topology. Maybe just return the new values.

            Assignee:
            Oleg Pudeyev (Inactive)
            Reporter:
            Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: