[SERVER-85524] Re-enable analyze_shard_key_database_and_shard_versioning.js targeting secondaries node Created: 22/Jan/24 Updated: 25/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Enrico Golfieri | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Analyze shard key can be executed against both a primary node or a secondary. This is tested in analyze_shard_key_database_and_shard_versioning where a movePrimary is added before the command is executed to confirm this behaviour is respected also in case the primary shard changes. However, after This is causing a known issue ( To temporarily bypass this issue, which will be solved as part of This ticket should remove the check and enable the test again.
|