mc admin uncordon

Syntax

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

Parameters

ALIAS

Required

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

NODE

Required

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

For example: node1.example.com:9000

Global flags

This command supports any of the global flags.

Examples

Uncordon a node after maintenance

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

1. Uncordon the node:

   mc admin uncordon myaistor node1.example.com:9000

   The command reports that the cordoned node is not reachable:

   Uncordon request handled, but there were errors: node1.example.com:9000
     node1.example.com:9000: peer is not reachable (hint: cordoned nodes must be manually restarted first)

   This is expected. The command still clears the cordon state.

2. Restart the MinIO AIStor process on the cordoned node:

   sudo systemctl restart minio

Verify node status after uncordoning

After uncordoning, verify the node has rejoined the cluster:

mc admin info myaistor

The node should display as Online in the command output.

Permissions

This command requires the admin:ServiceCordon permission.

Behavior

Error handling

If the uncordon operation encounters errors on some peer nodes, the command returns with state uncordoned-with-errors and lists the affected nodes. An error for the node you are uncordoning is expected while that node is cordoned: the command still clears the cordon state, and you restart the node next. An error for any other node usually means a network problem between nodes.

State persistence

After a successful uncordon, MinIO 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.

Node state after uncordon

mc admin uncordon makes the cluster willing to accept the node back; it does not bring the node up. The node displays as Offline in mc admin info until you restart the MinIO AIStor process on it.