mongod parameters specified at build variant level are not set on old binaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • ALL
    • Hide
      1. Run this multiversion test locally from the master branch:

      buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=0.5 --dbpath=/tmp/testpath --mongodSetParameters='{internalQueryFrameworkControl: forceClassicEngine}' --jobs=1 --suite=sharding_last_lts_mongos_and_mixed_shards ./jstests/ sharding/query/lookup_targeting.js

      Show
      Run this multiversion test locally from the master branch: buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=0.5 --dbpath=/tmp/testpath --mongodSetParameters='{internalQueryFrameworkControl: forceClassicEngine}' --jobs=1 --suite=sharding_last_lts_mongos_and_mixed_shards ./jstests/ sharding/query/lookup_targeting.js
    • 161
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When we test multiversion scenarios, the parameters set at the build variant level (like this one), are not being set during the instantiation of old mongod binaries (i.e. mongod-8.0, mongod-7.0, etc).

      According to this message, this prevents setting a parameter that could not exist on a mongod version. However, this is error-prone solution since some tests may expect a parameter to be set on all the mongod binaries of a cluster.

      For instance, we have had a test failure (the BF is linked to this ticket) since we expected all binaries on a cluster to have set this parameter.

            Assignee:
            Steve McClure
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: