[SERVER-13198] must disallow db.eval on config DB Created: 14/Mar/14 Updated: 06/Dec/22 Resolved: 23/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.9, 2.6.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | mongos> db.eval('sh.setBalancerState(false)') Now first config server has balancer stopped true but the other two have it as false. |
||||
| Participants: | |||||
| Description |
|
I can run db.eval('sh.command') on config DB and cause an update to just the first config server. |