Configuring the NodeSync refresh data interval

Tune the configuration option if necessary to adjust the frequency of refreshing NodeSync status data in OpsCenter Monitoring.

Tune the configuration option if necessary to adjust the frequency of refreshing NodeSync status data in OpsCenter Monitoring.

cluster_name.conf

The location of the cluster_name.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf

address.yaml

The location of the address.yaml file depends on the type of installation:
  • Package installations: /var/lib/datastax-agent/conf/address.yaml
  • Tarball installations: install_location/conf/address.yaml

opscenterd.conf

The location of the opscenterd.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/opscenterd.conf
  • Tarball installations: install_location/conf/opscenterd.conf

Configuration option for NodeSync

The refresh period configuration option represents the period of time (in seconds) between each NodeSync service refresh of status data from the NodeSync metrics table. The default is 300 seconds (5 minutes). If a status refresh takes 2 minutes to complete, the refresh period timer starts again and refreshes the NodeSync Status view after another 5 minutes.
[nodesync] refresh_period
The period of time in seconds between each NodeSync Service refresh of status data from the NodeSync metrics table. Default: 300 (5 mn).

Procedure

  1. Open opscenterd.conf for all clusters, or cluster_name.conf for a specific cluster.
    If necessitated by your environment, open address.yaml for editing and configure at the node level. Do so for every node that requires a specific configuration override.
  2. Set the following option for your environment requirements in the [nodesync] section:
    The following configuration example triples the refresh interval from 5 minutes (300 seconds) to 15 minutes (900 seconds):
    [nodesync]
    refresh_period=900
  3. Restart opscenterd.
  4. Optional: If you made changes to address.yaml, restart the DataStax agents.