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

Provide more documentation and helper functions for case where feature flag checks could be run when fCV is uninitialized during initial sync

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.0.4
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Replication
    • Fully Compatible
    • v7.0
    • Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13

      As part of PM-3236 it would be helpful to do an audit of the FCV.getVersion and the FeatureFlag::isEnabled, isEnabledAndIgnoreFCVUnsafe, isEnabledAndIgnoreFCVUnsafeAtStartup, isEnabledOnVersion and any other relevant FCV/feature flag helper functions just to make sure they're being used properly, and also to get a better sense of how engineers are using them and what improvements to the FCV/feature flag infrastructure should be made.
      ^ Moved to separate ticket SERVER-81225 for now since these two tasks are separate/have different urgencies

      Specifically we should also look into providing more guidance and helper functions around the situation described in https://jira.mongodb.org/browse/SERVER-79330 (for example, adding a helper function for if the use case needs to wait until FCV is initialized before checking the feature flag, or otherwise providing more documentation)

            Assignee:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Reporter:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: