SERVER-139117Open

Concurrent setParameter calls can leave query-memory load shedding stopped or misconfigured

Items 2 and 3 of SERVER-138793. {{ServerParameter::set()}} runs validate, store and {{on_update}} with no lock across them ({{server_parameter_with_storage.h:291-303}}), and {{CmdSet}} takes no lock around it. The two load-shedding knobs rely on that sequence being atomic, and it is not. *Start/stop lost update.* {{onUpdateQueryMemoryLoadSheddingEnablement}} acts on the {{newPercent}} of its own call, and {{startQueryMemoryRssMonitor}} checks {{sheddingActive()}} before taking {{holder.mutex}}.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.