BugZero | MongoDB BugID 394585 - Turn on non-strict parsing for replication IDL str...

MongoDB - Defect ID: 394585

Turn on non-strict parsing for replication IDL structs that are persisted or parsed from messages from other nodes

MongoDB - Defect ID: 394585

Turn on non-strict parsing for replication IDL structs that are persisted or parsed from messages from other nodes

Last updated on 10/27/2023

Overall: 5.85.8

Severity: 6.46.4

Community: 4.74.7

Lifecycle: 9.19.1

What is the BugZero Risk Score?

Vendor details

Priority: Major - P3
Status: Closed

Overall: 5.85.8

Severity: 6.46.4

Community: 4.74.7

Lifecycle: 9.19.1

What is the BugZero Risk Score?

Vendor details

Priority: Major - P3
Status: Closed

Info

Strict parsing will make it difficult to add fields in the future due to mixed version replica sets and upgrade/downgrade. Examples of this so far are (though may not be restricted to): minValid rollbackId OplogEntry

Top User Comments

Steps to Reproduce

5.9Defect ID: 2956672
Some time-series tests implicitly rely on measurement insertion order for unordered inserts when checking bucket catalog stats
6.14Defect ID: 2965528
Remove push, publish_packages, and crypt_push tasks from Graviton 4 variants in v7.0 and v8.0
6.14Defect ID: 2947969
[SBE] Release storage engine resources when saveState() or restoreState() throws
5.68Defect ID: 2919474
StackLocator broken by v5 toolchain ASAN
5.88Defect ID: 2968769
Make new write path helper functions use acquireAndValidateBucketsCollection instead of acquireCollection

Ready to prevent the next vendor outage?

Get a demo

OPERATIONAL DEFECT DATABASE

MongoDB - Defect ID: 394585

Turn on non-strict parsing for replication IDL structs that are persisted or parsed from messages from other nodes

MongoDB - Defect ID: 394585

Turn on non-strict parsing for replication IDL structs that are persisted or parsed from messages from other nodes

Last updated on 10/27/2023

Vendor details

Vendor details

Description

Info

Top User Comments

Steps to Reproduce

Links

Top MongoDB defects by risk score

Ready to prevent the next vendor outage?