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

prohibit choosing ourselves as a sync source

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 3.4.0-rc0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2016-10-10
    • 0

    Description

      We should add back in the restriction that we cannot choose ourselves as a sync source. This can sometimes happen when chaining is disallowed and a primary steps down.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26403 Clean primary states on stepdown

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-23663 New primary syncs from chosen node to catch up with timeout

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26423 ignore chainingAllowed setting when choosing sync source in catch-up mode

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              milkie@mongodb.com Eric Milkie
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: