Metadata Stores

Note

Metadata store management via configure.flexfs is an Enterprise-only feature. Community edition configures its metadata server address directly during free.flexfs init creds.

A meta store is a registration record in the admin server that represents a running meta.flexfs metadata server instance. Volumes reference a meta store by ID to determine which metadata server holds their filesystem metadata (inodes, directory entries, attributes, ACLs, and extended attributes).

Meta Store Fields

Field	Flag	Type	Required	Description
id	—	integer	auto	Unique identifier (auto-assigned)
provider_code	--providerCode	string	create	Provider code where the metadata server is deployed
region_code	--regionCode	string	create	Region code where the metadata server is deployed
address	--address	string	create	Server address in host:port format
token	--token	string	—	Authentication token (UUID, auto-generated if omitted)

Creating a Meta Store

configure.flexfs create meta-store \
  --providerCode aws \
  --regionCode us-east-1 \
  --address meta-host:443

If --token is omitted, the admin server generates a UUID automatically. This token is used to authenticate the metadata server’s connection to the admin server. You will need this token when initializing the meta.flexfs credentials on the metadata server host.

Specifying a Token

configure.flexfs create meta-store \
  --providerCode aws \
  --regionCode us-east-1 \
  --address meta-host:443 \
  --token $TOKEN

Viewing the Token

After creating a meta store, retrieve the auto-generated token with show:

configure.flexfs show meta-store <id>

The full detail view includes the token field, which is not shown in list output.

Updating a Meta Store

Update the server address or rotate the authentication token:

configure.flexfs update meta-store <id> --address new-meta-host:443
configure.flexfs update meta-store <id> --token $TOKEN

Caution

After updating a meta store’s token, update the credentials on the corresponding meta.flexfs server to match. The metadata server will fail to authenticate with the admin server until its token is updated.

Listing Meta Stores

configure.flexfs list meta-stores

The list view shows id, provider_code, region_code, and address. The token field is hidden in list output for security.

Deleting a Meta Store

configure.flexfs delete meta-store <id>

Note

A meta store cannot be deleted while it is referenced by any volume. The server will reject the request with a foreign key constraint error. Retire or delete all volumes using the meta store first. Deleting a meta store removes only the configuration record — the metadata server process and its data are not affected.

Linking to a Metadata Server

After creating a meta store record in the admin server, you must configure the actual meta.flexfs process to connect back to the admin server. On the metadata server host:

meta.flexfs init creds \
  --adminAddr admin-host:443 \
  --token $TOKEN

The token here is the one generated (or specified) when creating the meta store. This establishes a trusted link between the metadata server and the admin server, allowing the metadata server to receive volume assignments and report health.

See Metadata Server Setup for complete configuration instructions.

Provider and Region

The provider_code and region_code fields on a meta store record where the metadata server is physically deployed. This information is used for:

• Operational visibility — understanding the geographic distribution of metadata servers
• Resource planning — matching volumes to nearby metadata servers for lower latency

When creating volumes, choose a meta store in a region close to your mount clients to minimize metadata RPC latency.