[SERVER-23803] Add additional logging to debug csrs_upgrade test failures Created: 19/Apr/16 Updated: 16/May/16 Resolved: 16/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16) | ||||
| Participants: | |||||
| Linked BF Score: | 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. |