Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-64750

Only check isSelf for reconfigs when we have to

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc1, 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Repl 2022-08-08, Repl 2022-08-22, Repl 2022-09-05
    • 0

      Currently we depend on sameConfigContents to determine whether we need to check isSelf for a reconfig. This function only ignores the 'version' and 'term' fields of the config. However, there are other cases (e.g. removing the newlyAdded field for a node) where checking isSelf is not necessary. This ticket is to come up with a more precise condition for when isSelf check is necessary for a reconfig and to eliminate unnecessary isSelf calls.

            Assignee:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: