[SERVER-31884] Disable toggle_feature_compatibility.js workload in stepdown suites Created: 08/Nov/17 Updated: 30/Oct/23 Resolved: 10/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Justin Seyster |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
In the toggle_feature_compatibility.js FSM workload, setFeatureCompatibilityVersion upgrades can take a long time, because they need to add UUIDs to a large number of collections. As a result, it is very probable for the command to get interrupted more than three times by primary stepdowns. As a result, the setFeatureCompatibilityVersion command gives up retrying, even though it was making forward progress. There's no failure (if setFeatureCompatibilityVersion kept retrying, it would eventually succeed), and we don't consider this a normal user scenario, so we are just going to remove this test from stepdown suites for now. |
| Comments |
| Comment by Githook User [ 08/Nov/17 ] |
|
Author: {'name': 'Justin Seyster', 'username': 'jseyster', 'email': 'justin.seyster@mongodb.com'}Message: |