[SERVER-74190] Correctly propagate the featureFlagResilientMovePrimary status in random_DDL_operations.js Created: 20/Feb/23 Updated: 29/Oct/23 Resolved: 21/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 6.3.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.3
|
||||||||
| Sprint: | Sharding EMEA 2023-02-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 136 | ||||||||
| Description |
|
Settings defined in the FSM's data are initialized to their definition value when the FSM's processes are started, implying that any change applied in the setup function is lost. The proper way to rely on changes applied in the setup function phase is to avoid the initialization to their default when the FSM test is instantiate. The random_DDL_operations.js test skips movePrimary operation when the non-resilient version is enabled, but the feature flag status is not propagate properly to the FSM's processes, causing the the non-resilient movePrimary to run. The problem is relatively easy to occur on the 6.3 branch, but multi-version suites on master may trigger the same. |
| Comments |
| Comment by Githook User [ 21/Feb/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Githook User [ 21/Feb/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |