Secondaries running 2.0 not detected by 2.4 mongos during 2.2 -> 2.4 upgrade process

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.4.0-rc1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      No mongod 2.0 processes should be running when the 2.2->2.4 upgrade process takes place and the 2.4 mongos attempts to detect any running processes and order to abort safely.
      However with secondaries (i haven't yet tried it to see what happens if they are primaries) running 2.0 the mongos seems to miss them and continue the upgrade anyway.

        1. bug1.js
          2 kB

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Michael O'Brien
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: