Operational Defect Database
BugZero found this defect 65 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2609683
Investigate why change_streams passthrough suites fail with replica set endpoint
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Before SERVER-85770 changes, RouterServer was only added at MongoD in two situations: If we deploy a shard and gEmbeddedRouter is enabled and we pass a --routerPort. If gFeatureFlagAllMongodsAreSharded and gEmbeddedRouter are enabled. New change_streams passthrough suites were running only enabling gFeatureFlagAllMongodsAreSharded, not gEmbeddedRouter. Thus, all those tests were validated with a ReplicaSet without having ClusterRole::RouterServer, possibly breaking some assumptions. clusterRole = {ShardServer, ConfigServer} Once SERVER-85770 was committed, it has made RouterServer not depend on the gEmbeddedRouter feature flag, and once gFeatureFlagAllMongodsAreSharded is enabled on those new suites, we will always have: clusterRole = {ShardServer, RouterServer, ConfigServer} With that, all new change streams suites with replica set endpoint are failing.
Top User Comments
Steps to Reproduce
