Resmoke should only enable feature flags linked to the (mongod/mongos/mongocryptd) binary

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.3.0-rc0
    • Component/s: None
    • None
    • DevProd Correctness
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running a jstest suite with all feature flags enabled, for each feature flag resmoke passes --setParameter featureFlagXYZ=true to mongod, mongos and mongocryptd.

       

      The problem is that if the IDL for a feature flag is not linked to one of those binaries (as it may be irrelevant, specially often for mongocryptd), resmoke tries to enable it anyway, so jstest initialization fails with "Failed global initialization: BadValue Unknown --setParameter 'featureFlagXYZ'".

       

      SERVER-64540, SERVER-65843, SERVER-70561, SERVER-96887 are tickets that got reverted due to this issue.

      It also adds friction to code ownership of feature flags across server teams (SERVER-117325).

       

      resmoke should not pass --setParameter featureFlagXYZ if the binary doesn't link featureFlagXYZ.

            Assignee:
            Unassigned
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: