-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2026-11-23
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The receiving node must verify the HMAC signature against its key cache before adopting the gossiped $clusterTime. However, if the node has not loaded its HMAC keys yet, then it can't validate the $clusterTime. As written today, the node fails the request rather than continuing to process the command. (Note: the $clusterTime is just metadata, not the command itself.)
Why aren't the keys loaded? That requires a majority read. If a PSA primary is starting up and its secondary is down, then it cannot establish a majority point, so it is permanently blocked.
What clients are affected? Any authenticated client without the advanceClusterTime privilege, which is all ordinary application traffic.