What happens when you restart services via the UI after making a Central Configuration change?

Version/Environment:

This applies to all versions of Domino.

Issue:

After making a central configuration change, the setting did not get applied immediately.

Resolution:

When Admins change a Central Configuration setting by going to Admin > Advanced > Central Configuration, they must restart services for the change to take effect. Once restarted, the frontend servers are restarted, including the executor, frontend, and dispatcher containers.

Notes/Information:

When should I restart services to prevent downtime? 

When you restart services, the frontend servers are restarted as a rolling restart. This means the pods shut down and restart one at a time. This method prevents service outages and ensures high-availability by always having a pod running. That being said, out of caution, some customers do prefer to do restarts after-hours in case there is a disruption in service. 

Will the config change be applied to all my projects?

Central config changes may not apply to projects created prior to changing the setting. For example, let’s say you changed the default setting for com.cerebro.domino.workspaceAutoShutdown.globalMaximumLifetimeInSeconds from the default 259200 seconds (72 hours) to 28800 seconds (8 hours). Workspaces that were started before the change will not be limited to the new 8-hour setting. If you wish for the new setting to apply, there will be no choice but to recreate the workspace.