-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-03-31, CAR Team 2025-04-14
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The `system.profile` collection is a special collection, which can be created on each node during profile enabling via the command `setProfilingLevel`. With specific behaviour, for example as this collection is not replicated, it can cause different issue in the test consistency validation. More info can be found also in in https://jira.mongodb.org/browse/SERVER-97721.
Initially it was considered that the issue exists only when featureFlagReplicaSetEndpoint enabled, but additional tests have shown, that it's also possible to catch this problem in more common case, without featureFlagReplicaSetEndpoint.
- related to
-
SERVER-97721 system.profile visibility inconsistency in sharded cluster after db.setProfilingLevel
-
- Backlog
-