Disabling and enabling replication for individual client nodes

Disabling replication for a client node causes the server to skip the node during replication processing. Disabling replication for a client node can be useful if, for example, data that belongs to the node is corrupted or contaminated. After the problem is fixed, you can enable replication.

About this task

To determine the replication state of a node, issue the QUERY NODE command.

Procedure

To disable replication for a node, issue the UPDATE NODE command and specify REPLSTATE=DISABLED. For example, to disable replication for NODE1, issue the following command:
```
update node node1 replstate=disabled
```
To enable replication for a node, issue the UPDATE NODE command and specify REPLSTATE=ENABLED. For example, to enable replication for NODE1, issue the following command:
```
update node node1 replstate=enabled
```

What to do next

Remember: If you disable replication for a client node while data that belongs to the node is being replicated, the replication process is not affected. Replication of the data continues until all the data that belongs to the client node is replicated. However, replication for the client node will be skipped the next time that replication runs.