Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16)
-
0
Description
The csrs upgrade tests sometimes fails with an ExceededTimeLimit error because an operation on the config server timed out. This seems to happen when one of the secondaries doesn't fine a sync source for a long time (about a minute in the tests I've looked at closely), which then causes majority reads and writes to time out. This ticket is to add logging to figure out why the secondary goes so long without a sync source.