Administrator’s Command Line Guide

4.7. Monitoring the Status of Replication Parameters
Event Severity Description
CS#<N> has not registered dur-
ing the last T sec and is marked
as inactive/offline
MDS warn Generated when the chunk server CS#<N> has been
unavailable for a while. In this case, the chunk server
first gets marked as inactive. After 5 minutes, the
state is changed to offline, which starts the automatic
replication of data to restore the replicas that were
stored on the offline chunk server.
Failed to allocate N replicas
for ‘path‘ by request from
<<addr>:<port>> - K out of M
chunks servers are av ailable
MDS warn Generated when the cluster cannot allocate chunk
replicas, for example, when it runs out of disk space.
Failed to allocate N replicas
for ‘path‘ by request from
<<addr>:<port>> since only K
chunk servers are regis tered
MDS warn Generated when the cluster cannot allocate chunk
replicas because not enough chunk servers are reg-
istered in the cluster.
4.7 Monitoring the Status of Replication
Parameters
When you configure replication parameters, keep in mind that the new settings do not come into effect im-
mediately. 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:
1. Run the vstorage -c <cluster_name> top command.
2. Press the V key on your keyboard 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
57