[DOCS-10586] Enabling profiler causes restart, but the ops manager manual does not mention that Created: 27/Jul/17 Updated: 29/Oct/23 Resolved: 08/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lungang Fang | Assignee: | Robert Justice (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 6 days ago | ||||
| Story Points: | 0.1 | ||||
| Description |
|
Customer found that the mongod process was restarted after he enabled the profiler. This is an expected behaviour. Actually, any mongod configuration change results in a restart. However, it is not documented. Can we add a note of this somewhere in the Ops Manager document? Thanks, |
| Comments |
| Comment by Robert Justice (Inactive) [ 08/Feb/18 ] |
|
Kay merged! |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'robertjustice@Roberts-MacBook-Air-3.local', 'name': 'Robert Justice'}Message: Added note that enabling profiling causes the mongod processes to restart. ( Review by Ravind. ( Comment by Louisa Berger. ( Review comment from Louisa Berger. ( |
| Comment by Louisa Berger [ 06/Feb/18 ] |
|
Let's move the concerns about how the Automation Agent is functioning to a feature request ticket, and keep this Docs ticket focused on the documentation of the current behavior. I see you've already found PRODUCT-534 – that's actually the best place to raise these issues, since then Product can actually prioritize them. Thanks! |
| Comment by John Page [ 06/Feb/18 ] |
|
This doesn't address the basic issue that we NEED to be able to turn profiling on and off without any restart. In production systems we enable it in the UI then disable manaully pending needing the turn it back on at some future point. |
| Comment by Louisa Berger [ 06/Feb/18 ] |
|
| Comment by Rohit Malik [ 16/Oct/17 ] |
|
I just enabled database profiling from automation and the mongodb instance got restarted, we should mention this in the documentation as this can cause a big issue on production systems being restarted without change request or correct communications. |
| Comment by Louisa Berger [ 08/Sep/17 ] |
|
The sslMode parameter is changed by a totally different procedure / codepath. The regular parameters will trigger a restart. Feel free to link any requests with our CLOUDP-13951 ticket! |
| Comment by John Page [ 08/Sep/17 ] |
|
Except automation does change other setParameter things without a rolling restart - specifically sslmode, I know it does it without a restart because when you change it - the mongod.conf file doesn't change until the next restart but the behaviour does. However as quite a few complaints have come in from the field I will hunt down or raise a PAIN ticket for this. |
| Comment by Louisa Berger [ 08/Sep/17 ] |
|
Yes, any parameter change will trigger a rolling restart. It's correct that MongoDB allows you to change this parameter via the setParameter command without a restart, but Automation does not currently support changing parameters via the setParameter command (not a bug). Future ticket here : https://jira.mongodb.org/browse/CLOUDP-13951 |
| Comment by James Broadhead (Inactive) [ 17/Aug/17 ] |
|
tbqh, I don't know – maybe louisa.berger does? |
| Comment by John Page [ 11/Aug/17 ] |
|
MongoDB does not need a restart to enable profiling and Ops Manager can modify parameters without a restart in some cases - so why does OM restart the instance (which is then probably no longer the primary and no longer NEEDS profiling on as it's now secondary) |