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

setFeatureCompatibilityVersion command can return before it applied the changes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.0-rc8
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Hide

      this[ lobster |https://logkeeper.mongodb.org/lobster/build/85197e12c3faddbd254675e593b18daa/test/5d336884be07c4080101133e#bookmarks=0%2C2147%2C2187%2C2282%2C2984]has marked the process c20523 is not updated at the moment mongos RSM targets it.

      Show
      this[ lobster |https://logkeeper.mongodb.org/lobster/build/85197e12c3faddbd254675e593b18daa/test/5d336884be07c4080101133e#bookmarks=0%2C2147%2C2187%2C2282%2C2984]has marked the process c20523 is not updated at the moment mongos RSM targets it.
    • Sharding 2019-08-26, Sharding 2019-09-09
    • 22

      setFeatureCompatibilityVersion command can return before all the nodes in config cluster are downgraded as this is tied to writing the featureCompatibilityVersion document.
      The follow-up attempt to connect to all config shard nodes can fail the mongos when it attempts to refresh shardRegistry

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: