Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 8.0.17
Component/s: None
Labels:
None

Assigned Teams:

Server Security
Operating System:
ALL
Linked BF Score:
0
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

This applies to mongod/s version 8.0.x.

Currently, a cluster running 8.0.x binaries in FCV 7.x will not reject attempts to run setClusterParameter with a "fleCompactionOptions" object containing fields that do not appear in the FLECompactionOptions IDL schema. Note that IDL parsing permits unknown fields because the IDL definition in v8.0 onwards is non-strict. This presents a problem when v7.x binaries are then introduced in the cluster, as v7.x binaries have a strict definition of FLECompactionOptions, and so will fail upon seeing unknown or incompatible fields.

Note that since ~~SERVER-95111~~, known fields that are in the v8.0 schema but are not in the v7.0 schema are already forbidden from being set whilst the server is in FCV 7.x.

depends on

SERVER-95157 Retain ignored fields list when parsing IDL structs

Backlog

is related to

SERVER-95111 Add FCV guard for fleCompactionOptions anchorPaddingFactor

Closed

SERVER-117012 [v8.0] Enable backward compatibility for 'compactAnchorPaddingFactor' and 'maxAnchorCompactionSize' fields of fleCompactionOptions cluster parameter

Needs Scheduling

related to

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

Blocked

Assignee:: Unassigned
Reporter:: Erwin Pe
Participants:: Erwin Pe
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Sep 25 2024 02:31:01 PM UTC
Updated:: Jan 16 2026 04:46:48 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates