-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.5.8
-
Component/s: None
-
None
-
(copied to CRM)
-
Empty show more show less
When the primary is unknown the maxStalenessReducer attempts to determine the server with the greatest lastWriteDate in order to calculate each server's staleness. There is a bug where the reducer currently assumes it will always be able to find such a server, which is not possible when working with an empty set of servers.
- is duplicated by
-
NODE-2646 Add coverage for valid maxStalenessSeconds with no viable servers
- Closed