Configuration via CLI
Table of Contents
ais config clusterais config node- Example: show config, update config
- Example: show specific config section (flat and JSON)
- Configuration inheritance
- Show configuration
- Update cluster configuration
- Update node configuration
- Reset configuration
- CLI configuration
There are two main configuration-managing commands, each with multiple subcommands:
ais config- show and update configurationais show config- show configuration
As always, subcommands will reveal themselves via tab completion (
<TAB-TAB>).
In brief:
ais config showis an alias forais show config— both can be used interchangeably.
Here are a few usage examples:
ais config cluster
ais config node
Example: show config, update config
More examples:
Note: Single quotes are strongly recommended when values contain spaces, wildcards, or double quotes.
Example: show specific config section (flat and JSON)
Configuration inheritance
AIS supports configuration inheritance with local override.
At any point in time there is a single, protected and replicated version of the cluster configuration. When a new cluster gets deployed, all nodes inherit the same initial configuration with identical default values. When a new node joins the cluster, it receives the current version of the cluster configuration.
However, you can select any node and override any inherited value. Note that if the corresponding value later changes at the cluster level, the node’s override takes precedence — the cluster-level update won’t apply to that node.
In other words, overriding inherited configuration on the node level breaks future inheritance for that setting.
Use
ais config resetto remove all previous overrides.
All configuration updates are persistent by default. Use the --transient flag to update in memory only (changes won’t persist across reboots).
See also: AIStore Configuration
Show configuration
Target nodes have the
tprefix; gateways (proxies) have thepprefix.
Cluster configuration
ais show config cluster [CONFIG_PREFIX]
Display the cluster configuration. If CONFIG_PREFIX is given, only configurations matching the prefix will be shown.
Node configuration
ais show config NODE_ID [inherited | local] [CONFIG_PREFIX]
Display the node’s configuration. Node configuration consists of two parts:
- inherited — cluster configuration (may include local overrides)
- local — node-specific settings that override cluster defaults
If CONFIG_PREFIX is given, only configurations matching the prefix will be shown.
When showing inherited config, the output includes an extra column with global values:
-— local and global values are the same (not overridden)N/A— option is local-only and doesn’t exist in global config
Examples
Show node’s local configuration
Note: Examples in this section show local-playground paths and ports; production deployments will differ.
Show node’s inherited configuration
Show cluster LRU config section
Update cluster configuration
ais config cluster NAME=VALUE [NAME=VALUE...]
Use tab completion to discover available settings:
Specify name-value pairs separated by space or =. To see the current value before updating, just press Enter:
Set multiple config values
Update node configuration
ais config node NODE_ID [inherited | local] NAME=VALUE [NAME=VALUE...]
Steps:
- Select a node (or use
<TAB-TAB>to complete) - Select
inheritedto update cluster-level values, orlocalfor node-specific settings - Specify name-value pairs
When updating inherited values, all previous overrides can be undone with
ais config reset.
Set multiple config values
Reset configuration
ais config reset [NODE_ID]
Reset configuration back to cluster defaults, removing all local overrides.
CLI configuration
The CLI tool has its own configuration, separate from cluster configuration.
Note: Examples in this section show local-playground paths and ports; production deployments will differ.
Show CLI configuration
ais config cli [--path] [--json]
Display the current CLI configuration. Use --path to show only the config file location.
Update CLI configuration
ais config cli NAME=VALUE [NAME=VALUE...]
The configuration file is updated only if all new options are applied without errors. If an option name doesn’t exist or a value is incorrect, the operation is aborted.