Detail how setting FeatureCompatibilityVersion can be affected on merged config + shard server

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC
    • 4
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Al lot of FCV code is conditioned on Config server. The sequence of applying the FCV is also different on Config and shard - if this sequence is fully preserved at some moment the FCV at Config and shard would be different, but it is a global property.

            Assignee:
            [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: