[v8.0] Setting cluster parameter 'fleCompactionOptions' in mixed binary scenarios may last forever when setting an unknown field

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.0.17
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-01-19, CAR Team 2026-02-02
    • 200
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      Setting cluster parameter fleCompactionOptions in a mixed binary sharded cluster (config server on v8.0, one or more shards on v7.0) can cause the setClusterParameter command to never complete when the parameter value includes an unknown field. The config server accepts the parameter, but shards running v7.0 reject it and the coordinator retries indefinitely.

       

      Background

      The FLECompactionOptions IDL definition changed its strictness between versions:

      • In v7.0, FLECompactionOptions is strict:true, so extra/unknown fields cause validation to fail.
      • In v8.0, FLECompactionOptions was changed to strict:false as part of SERVER-85747, so unknown fields are silently accepted.

      setClusterParameter is coordinated by the config server:

      1. The config server parses and validates the request.
      2. A SetClusterParameterCoordinator is instantiated and propagates the setClusterParameter command to all shards.
      3. On failure, the coordinator retries the operation until it succeeds.

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: