Details
-
New Feature
-
Resolution: Gone away
-
Unknown
-
None
-
1.6.0
-
None
-
None
Description
Similar to https://jira.mongodb.org/browse/PYTHON-1434
Go Driver should have a retry option when receiving a bad ClusterTime. Otherwise, similar issue is observed:
2021-08-11T01:27:14.161Z I COMMAND [conn27172109] command admin.$cmd appName: "<redacted>" command: isMaster { ismaster: 1, $clusterTime: { clusterTime: Timestamp(1628645233, 6), signature:
{ keyId: 0, hash: BinData(0, 0000000000000000000000000000000000000000) }}, $db: "admin", $readPreference:
{ mode: "primary" }} numYields:0 ok:0 errMsg:"Cache Reader No keys found for HMAC that is valid for time:
{ ts: Timestamp(1628645233, 6) }with id: 0" errName:KeyNotFound errCode:211 reslen:315 protocol:op_msg 2ms
Attachments
Issue Links
- related to
-
DRIVERS-1904 Handle invalid $clusterTime documents when gossiping cluster time
-
- Backlog
-
- mentioned in
-
Page Loading...