mc admin uncordon

The mc admin uncordon command returns a cordoned node to active service after maintenance. This command notifies all other nodes in the cluster that the specified node is returning to service.

When you run mc admin uncordon, the command:

• Removes the node from the cluster’s internal list of cordoned nodes.
• Notifies all peer nodes that the target node is returning to service.
• Allows peer nodes to re-establish grid connections to the node.

See Node Maintenance for a complete procedure on cordoning and uncordoning nodes.

mc admin [GLOBALFLAGS] uncordon ALIAS NODE

Required

The alias of the AIStor cluster containing the node to uncordon.

Required

The address of the node to uncordon, in the format hostname:port.

For example: node1.example.com:9000

This command supports any of the global flags.

The following example demonstrates the complete workflow for returning a cordoned node to service:

1. Restart the AIStor process on the cordoned node:

   sudo systemctl restart minio
   

2. Uncordon the node:

   mc admin uncordon myaistor node1.example.com:9000
   

The command returns:

Node uncordoned successfully

After uncordoning, verify the node has rejoined the cluster:

mc admin info myaistor

The node should display as Online in the command output.

This command requires the admin:ServiceCordon permission.

If the uncordon operation encounters errors on some peer nodes, the command returns with state uncordoned-with-errors and lists the affected nodes. Common causes include:

• The cordoned node was not restarted before uncordoning.
• Network connectivity issues between nodes.
• The target node is still initializing.

If you receive errors indicating the node must be restarted first, ensure the AIStor process is running on the target node and try the uncordon command again.

After a successful uncordon, AIStor removes the node from the persisted cordon state in .minio.sys/cordoned.json. The node fully rejoins cluster operations after reconnecting to the grid.