-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: 2.2.0, 2.2.1
-
Component/s: None
-
None
-
None
-
C Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Summary
The change made in CDRIVER-5643 breaks cluster time handling for the first command sent out on a single-threaded client. The ticket stops cluster time gossiping on monitoring connections, and I presume that the single-threaded behaviour of using the actual server connection for monitoring commands breaks because of this.
Environment
Reproduced with libmongoc 2.2.1, but introduced in 2.2.0.
How to Reproduce
See this test failure observed in PHP: https://evergreen.mongodb.com/rest/v2/tasks/mongo_php_driver_2.x_test_debian11_php_8.3_test_mongodb_5.0_replicaset_auth_patch_e8bc627dbc6babfe4408e9563c6899e73ea9e885_6939685c22c7540007bc85a2_25_12_10_12_32_30/build/TestLogs/b4fb576c7f8162d066cb6103800886f3?execution=0&print_time=true
We expect the first aggregate command to include a clusterTime, but it's absent. The other tests that run afterwards correctly include a clusterTime.
- is caused by
-
CDRIVER-5643 Gossiping the cluster time from monitoring connections can result in loss of availability
-
- Closed
-
- is depended on by
-
PHPC-2655 Update to libmongoc 2.2.1 breaks cluster time gossiping for single-threaded drivers
-
- Blocked
-
- is related to
-
CDRIVER-5871 Implement Driver Session prose tests
-
- Backlog
-