Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add info about non-reloadable config options #1503

Merged
merged 3 commits into from
Oct 5, 2017
Merged

Add info about non-reloadable config options #1503

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7b54070
[skip ci] Add info on non-reloadable conf options
Oct 3, 2017
08432b2
[skip ci] Change for groups
Oct 3, 2017
09e9a1d
[skip ci] Update the list and description
Oct 4, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions doc/operation-and-maintenance/Reloading-configuration-on-a-running-system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,3 +14,11 @@ It's available as a safety mechanism for the rare case of a cluster-global reloa
on all nodes of the cluster.
The prerequisite is that the modified config file must be available on
all nodes at the same location (the location where MongooseIM expects its config file).

### Non-reloadable options
The following options' changes will be silently ignored:
* domain_certfile
* s2s
* all_metrics_are_global
* odbc
* ldap (tough can be changed, it can't be disabled/enabled)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/tough/though/