Reload MinIO cluster configuration to apply pool topology changes via SIGHUP (hot reload for config.yaml deployments)
domain: min.io · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Update config.yaml identically on ALL nodes (existing and new); verify identical copies with `shasum`.
Trigger a reload on each node by sending SIGHUP: `kill -HUP $(pgrep minio)`.
For systemd-managed deployments use `systemctl reload minio` instead.
Confirm the reload actually took effect in the SERVER LOGS - the reload command may report success even when the change was rejected.
Known gotchas
A config reload that adds a pool is rejected while a rebalance is active - run `mc admin rebalance stop ALIAS` first.
Pool removal via reload is only allowed after decommission reports Complete deployment-wide; otherwise reload errors with 'cannot reduce pool count while decommission is in progress'.
`kill -HUP`/`systemctl reload` can succeed even when the reload is rejected - always check server logs to confirm.
Wait until every queued decommission completes before removing multiple pools together.
Docs: decommission-server-pool.html and expand-minio-deployment.html at min.io/docs
Give your agent this knowledge — and 17,900+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?