The mc admin name command and its subcommands manage the cluster name for an MinIO AIStor deployment. The cluster name identifies the deployment in SUBNET registration and other administrative contexts. If you do not set a cluster name, MinIO AIStor automatically generates one at startup using the format <MythicalCreature><Element> (for example, “GriffinWave”, “UnicornFrost”, “KrakenStone”). The auto-generated name persists across restarts. You can also set the cluster name using the MINIO_SITE_NAME environment variable. When set with the environment variable, the name cannot be changed with mc admin name set.

The mc admin info command displays information on an MinIO AIStor server. For distributed MinIO AIStor deployments, mc admin info displays information for each node in the deployment. The output of the command resembles the following for a four-node cluster: ╭───────────────────────────────────────────────╮ │ MinIO Cluster: ● Online │ Edition: AIStor │ ╰───────────────────────────────────────────────╯ Capacity ╭───────────────────────────────────────────────────────────────────────────────╮ │ Used: 1.5 TiB / 12 TiB [██████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 12.5% │ │ Free: 10.5 TiB │ ╰───────────────────────────────────────────────────────────────────────────────╯ Servers ╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ ● node1.example.com:9000 │ Uptime: 3 days │ Drives: 4/4 │ Pool: 1 │ Version: 2025-01-01T00-00-00Z │ │ ● node2.example.com:9000★ │ Uptime: 3 days │ Drives: 4/4 │ Pool: 1 │ Version: 2025-01-01T00-00-00Z │ │ ● node3.example.com:9000 │ Uptime: 3 days │ Drives: 4/4 │ Pool: 1 │ Version: 2025-01-01T00-00-00Z │ │ ● node4.example.com:9000 │ Uptime: 3 days │ Drives: 4/4 │ Pool: 1 │ Version: 2025-01-01T00-00-00Z │ ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Pools ╭────────────────────────────────────────────────────╮ │ Pool │ Usage │ Stripe Size │ Sets │ │ 1st │ 12.5% (12 TiB) │ 16 │ 1 │ ╰────────────────────────────────────────────────────╯ Data Summary ╭────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Used: 1.5 TiB │ Buckets: 12 │ Objects: 48,000 │ Delete Markers: 0 │ Drives: 16 online / 0 offline │ Erasure Code: 4 │ ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ The ★ suffix on a node address in the Servers section identifies the current cluster-wide leader node. The leader is assigned dynamically and may change over the lifetime of the cluster, so the marked node can differ between runs of the command.

This guide summarizes internationalization APIs and features of Java SE.

Removes an IAM policy from the target MinIO AIStor deployment. Syntax Example The following command removes the policy readonly from the deployment at alias myaistor.

Documentation for the npm registry, website, and command-line interface

CONTENTS | PREV | NEXT Java Native Interface Specification Contents 1. Introduction Java Native Interface Overview Hi...

The mc admin user rm command removes an MinIO AIStor user on the target MinIO AIStor deployment. The mc admin user remove command has equivalent functionality to mc admin user rm. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command removes user myuser on the myaistor MinIO AIStor deployment:

Describes the use of scripting languages in Java applications, and how to access Java constructs from scripts.

Syntax Example The following command retrieves the anonymous access policy for the mydata bucket on the myaistor MinIO AIStor deployment: mc anonymous get myaistor/mydata Syntax Syntax The command has the following syntax:

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...