Correctly set the isUpgrading flag during rename for auth shards

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the implementation of authoritative rename we had to hardcode the isUpgrading flag to true since there is no way of discerning if we're in an FCV upgrade or not.

      This ticket is about implementing the proper feature flag checking to detect the upgrade scenario and set it on the rename coordinator calls.

            Assignee:
            Unassigned
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: