5.7. Monitoring Replication Parameters¶
When you configure replication parameters, keep in mind that the new settings do not come into effect immediately. For example, increasing the default replication parameter for data chunks may take some time to complete, depending on the new value of this parameter and the number of data chunks in the cluster.
To check that the new replication parameters have been successfully applied to your cluster:
vstorage -c <cluster_name> topcommand.
Press V to display additional information about the cluster. Your command output should look similar to the following:
# vstorage -c stor1 top connected to MDS#1 Cluster 'stor1': healthy Space: [OK] allocatable 200GB of 211GB, free 211GB of 211GB MDS nodes: 1 of 1, epoch uptime: 2h 21m CS nodes: 2 of 2 (2 avail, 0 inactive, 0 offline) License: PCSS.02444715.0000 is ACTIVE, 6399TB capacity Replication: 3 norm, 2 limit Chunks: [OK] 431 (100%) healthy, 0 (0%) degraded, 0 (0%) urgent, 0 (0%) blocked, 0 (0%) offline, 0 (0%) replicating, 0 (0%) overcommitted, 0 (0%) deleting, 0 (0%) void <...>
Check the Chunks field for the following:
When decreasing the replication parameters, look for chunks that are in the overcommitted or deleting state. If the replication process is complete, no chunks with these states should be present in the output.
When increasing the replication parameters, look for chunks that are in the blocked or urgent state. If the replication process is complete, no chunks with these states should be present in the output. Besides, when the process is still in progress, the value of the healthy parameter is less than 100%.
For more information on available chunk statutes, see Exploring Chunk States.