cluster
Cluster operations
cluster
Manage cluster operations.
Synopsis
arctic cluster <subcommand> [flags]Subcommands
| Subcommand | Description |
|---|---|
| init | Initialize cluster |
| identity | Show cluster identity |
| sync | Trigger synchronization |
| status | Show gossip status for diagnostics |
init
Initialize a cluster for legacy upgraded agents.
Usage
arctic cluster init [--force]Flags
| Flag | Description |
|---|---|
--force | Force reinitialize even if cluster exists |
Required Scope
urn:tillered:arctic:admin
Example
arctic cluster initOutput
Cluster initialized
Cluster ID: 01HABC...
Created By: 01HXYZ...
Oldest Peer: 01HXYZ...
Was Created: trueNotes
- Only needed for agents upgraded from older versions
- New agents have clusters initialized during bootstrap
- Use
--forceto regenerate the cluster ID (destroys existing cluster state)
identity
Show the cluster identity of a peer.
Usage
arctic cluster identityAuthentication
No authentication required (public endpoint).
Example
arctic cluster identityOutput
Peer ID: peer_01KBYMHC35F0N070F3XXMEZAZR
Public Key: qnGyPtol7lqzLYU3989eaC+K4xda0w9KXlcEOM9cSBQ=
License ID: lic_01KB45EYP1VJ1RZEGJDPKJQ9V4
Cluster ID: clu_01KBYMHMRJ92E090P50VRKG4ZC
Version: v0.1.0JSON Output
Use -j as shorthand for -o json:
arctic cluster identity -j{
"peer_id": "peer_01KBYMHC35F0N070F3XXMEZAZR",
"public_key": "qnGyPtol7lqzLYU3989eaC+K4xda0w9KXlcEOM9cSBQ=",
"license_id": "lic_01KB45EYP1VJ1RZEGJDPKJQ9V4",
"cluster_id": "clu_01KBYMHMRJ92E090P50VRKG4ZC",
"version": "v0.1.0"
}Use Cases
- Verify peer identity before adding
- Check license ID matches your cluster
- Retrieve public key for verification
sync
Trigger cluster synchronization.
Usage
arctic cluster syncRequired Scope
urn:tillered:arctic:admin
Example
arctic cluster syncOutput
Cluster sync triggeredBehavior
Triggers immediate:
- Gossip protocol heartbeats to all peers
- Configuration regeneration
- Subsystem processing (network, firewall, etc.)
Use Cases
- Force configuration update after changes
- Speed up propagation of new peers
- Troubleshoot synchronization issues
status
Show gossip status for cluster diagnostics.
Usage
arctic cluster statusRequired Scope
urn:tillered:arctic:admin
Example
arctic cluster statusOutput
Gossip Status
-------------
Local Peer: peer_01KBYMHC35F0N070F3XXMEZAZR
Cluster ID: clu_01KBYMHMRJ92E090P50VRKG4ZC
Peer Status:
peer_01KBYMD32Z2RVDE3G5Y9M530QR:
Last Seen: 2025-12-09 10:15:30 UTC
Status: healthy
Registry Hash: a1b2c3d4...
Registry:
Services: 5
Routes: 12
Hash: e5f6g7h8...JSON Output
arctic cluster status -jUse Cases
- Diagnose cluster synchronization issues
- Verify peer connectivity and health
- Check registry hash for drift detection
- Monitor gossip protocol state
See Also
- Clustering Concepts
- peers - Peer management