[SERVER-33645] Determine if splitvector.js should be blacklisted from the retryable_writes_jscore_stepdown_suite Created: 02/Mar/18 Updated: 29/Oct/23 Resolved: 20/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.8, 3.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Sharding 2018-04-09 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
jstests/core/splitvector.js occasionally times out on slower buildvariants in the retryable_writes_jscore_stepdown_suite. Even when successful, this is consistently the slowest test in this suite by a long shot (only ~8 min on Enterprise RHEL 6.2, > 1 hour on Linux DEBUG, ~ 1 hour on Windows 2008R2 DEBUG). This is expected because the test performs 10s of thousands of inserts and at least a dozen splitvectors. We can blacklist the test to avoid these timeouts, but the test itself isn't failing, and we'd lose some test coverage and some stepdown stress testing (longer runs can have ~400 failovers). The purpose of this ticket is to determine if its worth blacklisting splitvector.js or if we should find another way to avoid the timeouts. |
| Comments |
| Comment by Githook User [ 24/Aug/18 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 2ff63660cc0aff0dd54e84dcf4a346b848bf8213) |
| Comment by Githook User [ 20/Mar/18 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |
| Comment by Max Hirschhorn [ 05/Mar/18 ] |
|
jack.mulrow, I had noticed that the splitvector.js test spends 25 minutes on the Linux DEBUG builder doing non-batched inserts with w=majority. |