[SERVER-35090] Increase logging in the retryable_writes_jscore_stepdown_passthrough suite Created: 18/May/18 Updated: 06/Dec/22 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Backport Requested: |
v3.6
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Comments |
| Comment by James Wahlin [ 21/May/18 ] |
|
An initial attempt to raise query, command and replication verbosity failed. The latency introduced by the logging caused the retryable writes to exhaust retry attempts without succeeding, causing several tests to fail. Sending this ticket to sharding to see whether it would be worth putting a bigger effort into this. I don't think it is worth the effort for the attached BF which has occurred only once and on the 3.6 branch. |