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

Investigate v3.0 mongos and v3.2 cluster compatibility issues in jstests/sharding

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-rc3
    • Fix Version/s: 3.2.1, 3.3.0
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Sprint:
      Sharding D (12/11/15)

      Attachments

        Issue Links

        related to

        Bug - A problem which impairs or prevents the functions of the product. SERVER-21593 findAndModify on v3.0 mongos and v3.2 cluster can return stale config error to the user

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

        Bug - A problem which impairs or prevents the functions of the product. SERVER-21603 getLastError does not wait for replication on mongos v3.0 with mongod v3.2

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

        Bug - A problem which impairs or prevents the functions of the product. SERVER-21604 v3.0 mongos fails to ping config.mongos if config servers are v3.2

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

        Bug - A problem which impairs or prevents the functions of the product. SERVER-21660 serverStatus can stall and trigger timeout error on SCCC distributed lock with v3.0 mongos and v3.2 cluster

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

        Bug - A problem which impairs or prevents the functions of the product. SERVER-21661 v3.0 mongos and v3.2 cluster explain command are not compatible

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

          Activity

            People

            Assignee:
            renctan Randolph Tan
            Reporter:
            renctan Randolph Tan
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: