[SERVER-57191] Timeout in jstestfuzz due to printing WriteConflictException stack traces for all operations Created: 25/May/21 Updated: 29/Oct/23 Resolved: 28/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2021-06-14 | ||||
| Participants: | |||||
| Linked BF Score: | 48 | ||||
| Description |
|
In jstestfuzz_replication_write_conflicts.yml, we enable the parameter that prints WriteConflictException stack traces for all operations here. There was a build failure where 10 concurrent clients were running, 5 of which were running collection.remove({}) simultaneously on a collection of 100,000 documents. This caused a lot of WriteConflictExceptions to be thrown between these operations. These operations had to print stack traces, which caused a slowdown leading to the 2-hour timeout.
When the WTWriteConflictException or WTWriteConflictExceptionForReads fail points are used and hit, we should consider printing the stack traces for those operations, as opposed to using traceWriteConflictExceptions. This would reduce the amount of noise and logging produced in the test. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 28/May/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 27/May/21 ] |
|
Disable printing stacktraces for this test suite. |