-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.17, 4.2.5, 4.0.18
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.2, v4.0
-
Sharding 2020-09-07, Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-22, Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19, Sharding 2021-05-03, Sharding 2021-05-17
-
(copied to CRM)
-
142
Cluster time validation reads signing keys from cache , and if there are no keys the cache is refreshed by reading admin.system.keys collection. When the server is in the RECOVERING state it can not read from any collection including admin.system.keys collection. Hence any request, in particular isMaster from a monitoring agent returns meesages similar to
KeyNotFound) Cache Reader No keys found for HMAC that is valid for time: { ts: Timestamp(1585658632, 12) } with id: 6769620021938225153
- is depended on by
-
SERVER-54281 VectorClock's configTime can become greater than clusterTime after a signature failure
- Closed
- is related to
-
SERVER-55371 4.2.13 removed rs.initiate() return object time values
- Closed
-
SERVER-56471 Donor's listDatabases response missing operationTime
- Closed