[SERVER-43833] Check that setFeatureCompatibilityVersion is run on mongos in sharded environments. Created: 04/Oct/19 Updated: 08/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding, Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | James Phelan (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Sprint: | Sharding 2019-12-16 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
In a sharded cluster the setFeatureCompatibilityVersion command should be run only on a mongos it might be a good idea to reject this command if it is run on a mongod started with either the configsvr or shardsvr options. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |