Synchronizing the MRS Cluster Configuration
During MRS cluster O&M, after an administrator modifies service configuration parameters, the configuration status of the affected services changes to Expired. This status indicates that the updated parameters have not yet taken effect on the server. If a configuration update applies to all services in a cluster, or if a modification causes multiple services to enter the Expired or Failed state, the administrator must synchronize the configurations. Synchronization delivers the latest parameters to all affected services. After synchronizing, restart the service instances whose configurations have expired so the new settings can take effect. This section describes how to synchronize cluster configurations on the MRS console or MRS Manager.
Prerequisites
- The IAM users have been synchronized in advance. You can do this by clicking Synchronize next to IAM User Sync on the Dashboard page of the cluster details.
- You have logged in to MRS Manager. For how to log in, see Accessing MRS Manager.
Impact on the System
- After the cluster configurations are synchronized, you need to restart the services whose configurations have expired. During the restart, the corresponding services are unavailable.
- The instances whose configuration has expired are unavailable during restart.
Synchronizing Cluster Configuration
You can synchronize configurations using either the management console or MRS Manager.
This operation applies to MRS 2.x and earlier versions.
- Log in to the MRS console.
- On the Active Clusters page, select a running target cluster and click its name to go to the cluster details page.
- choose Configure > Synchronize Configuration in the upper right corner. Figure 1 Synchronizing configurations (using MRS 1.9.2 as an example)
- In the displayed dialog box, select "Restart services and instances whose configuration have expired" and click OK to restart the service whose configurations have expired.
When Operation successful is displayed, click Finish. The cluster is started.
Verification:
After synchronizing configurations and restarting services, check the configuration status of each service on the cluster dashboard page. If the configuration status of all services is Normal, the configuration synchronization is successful.
- Log in to FusionInsight Manager of the MRS cluster.
For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.
- Choose Cluster > Dashboard.
- For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from MRS Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.
- For MRS clusters of version 2.x or earlier, click Services and choose More > Synchronize Configuration.
- On this page, choose More > Synchronize Configuration.
- In the dialog box that is displayed, click OK.
- On the cluster dashboard page, choose .
- In the dialog box that is displayed, enter the password of the current login user and click OK.
- In the displayed dialog box, click OK.
You can click View Instance to open the list of all expired instances and confirm that the instances have been restarted.
Verification:
After synchronizing configurations and restarting services, check the configuration status of each service on the Cluster > Services page in MRS Manager. If the configuration status of all services is Synchronized, the configuration synchronization is successful.
FAQs
- Configuration synchronization failed
Common causes of configuration synchronization failures include abnormal service instances that prevent configuration delivery, network disconnections that disrupt communication between MRS Manager and instance nodes, or insufficient disk space on target nodes that prevents new configuration files from being written.
Check the status of each service on the Services page in MRS Manager, and restore any abnormal service instances. Check the cluster network connectivity and ensure each node has sufficient disk space. After rectifying the fault, synchronize the configuration again.
- Abnormal Service Status After Restarting Instances with Expired Configurations
Common causes of an abnormal service status after a restart include invalid values in newly modified configuration parameters that cause service startup failures, or interdependent parameters that were not updated simultaneously, resulting in configuration mismatches.
On MRS Manager, choose Cluster > Services to view the alarm information for the abnormal service, and locate the parameter issue based on the alarm details. After modifying the configuration parameters, synchronize the configuration and restart the instance.
- Persistent Configuration Expired Status After Synchronization
Synchronizing a configuration delivers parameters to the local configuration file of the service instance without triggering a restart. When the configuration status displays Expired, the configuration has been synchronized but will not take effect until you restart the service instance.
This is expected behavior. After synchronizing the configuration, restart the instance with the Expired configuration status. Once the restart completes, the configuration status changes to Synchronized.
Helpful Links
- For details about how to modify MRS role instance parameters, see Modifying MRS Role Instance Parameters.
- For details about how to modify OMS service configurations, see Modifying the OMS Service Configuration.
- For details about how to view MRS cluster alarms, see Viewing Alarms of an MRS Cluster.
