[SERVER-35903] Free monitoring doesn't allow disabling from the shell without enabling it first Created: 28/Jun/18 Updated: 29/Oct/23 Resolved: 13/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.1, 4.1.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Ramon Fernandez Marina | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.0
|
||||
| Participants: | |||||
| Description |
|
While one can easily disable free monitoring via the config file, starting up a vanilla 4.0 mongod and running db.disableFreeMonitoring() has no effect – one has to enable it first and then disable it. Would be handy to allow going from the "undecided" state to disable from the shell directly. |
| Comments |
| Comment by Githook User [ 13/Jul/18 ] |
|
Author: {'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: (cherry picked from commit 5a7537b07dbf7d8db74531632dc06883042b4234) |
| Comment by Githook User [ 13/Jul/18 ] |
|
Author: {'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: |