Loading...
Loading...
In SERVER-101748, a new non-optional field was added to SetClusterParameterCoordinatorDocument. This change is not backward compatible because documents persisted by older binaries do not contain this field, so when a node is upgraded and attempts to read an existing coordinator document, deserialization fails and the node crashes because the required field is missing from the stored document.
xgen-internal-githook commented on Wed, 7 Jan 2026 18:11:02 +0000: Author: {'name': 'wolfee', 'email': 'adam.farkas@mongodb.com', 'username': 'wolfee001'} Message: SERVER-116294 SetClusterParameterCoordinatorDocument crash on upgrade due to new non-optional field missing (#45965) GitOrigin-RevId: 61f2f7b2d25791e5e340c05f267d6fce106f4c34 Branch: master https://github.com/mongodb/mongo/commit/3400c2ac93909eef00370d245eb19b3af0755b15
TEST_F(SetClusterParameterCoordinatorTest, TestOldDoc) { auto oldDoc = BSON(SetClusterParameterCoordinatorDocument::kPhaseFieldName << "unset" << SetClusterParameterCoordinatorDocument::kParameterFieldName << BSONObj{} << "_id" << BSON("coordinatorType" << "setClusterParameter")); SetClusterParameterCoordinator scp(oldDoc); }
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.