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

Revisit propagation of VersionContext to FeatureFlagAllMongodsAreSharded checks

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since FeatureFlagAllMongodsAreSharded is fully disabled, it's use in the codebase has not been fully adapted to rely on the proper VersionContext during checks. This was done to avoid polluting the codebase by propagating the VersionContext across multiple layers, just to check a feature flag that is disabled and might be a candidate for deprecation (note that the All Clusters Sharded Intiative has been discontinued).

      The use of FeatureFlagAllMongodsAreSharded should be revisited in case we decide to enable it at some point. 

            Assignee:
            Unassigned Unassigned
            Reporter:
            robert.sander@mongodb.com Robert Sander
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: