Cluster nodes manage database and application membership. They do not promise automatic workload scheduling, geographic routing or seamless autoscaling.
開始前の準備
Private network reachability between nodes.
Administrator API token for the node being attached.
Compatible Callaba versions and a current configuration backup.
設定の説明
運用者に必要なコントロールだけを説明し、内部フィールド名や実装イベントは表示しません。
Node identity
Describe the trusted member.
- Name
Operator-facing node name.
- Node type
Master, Slave or Test role supported by the UI.
- Private host
Reachable private address used between nodes.
Avoid a public address when a private path is available.- API token
Administrator token used to establish trusted management.
Treat it as a secret.- Active
Lifecycle state of the registered node.
安全な初回ワークフロー
- 01
Back up the current configuration and verify private network connectivity.
- 02
Create the node with its intended role, private host and administrator token.
- 03
Attach the node and wait for membership to settle.
- 04
Start it and verify reachability plus the expected database membership.
- 05
Test detach and recovery procedure outside a production incident.
ワークフロー例
Add a trusted slave node
A self-hosted deployment needs a supported additional cluster member.
構築手順
- 1
Confirm compatible versions, backup and private connectivity.
- 2
Register the Slave with its private host and token.
- 3
Attach and start the node in a controlled window.
- 4
Verify node state and database membership before using it operationally.
結果を確認
- The node is reachable over the intended private path.
- Role and lifecycle state match the planned topology.
- Attach/detach operations produce the expected membership state.
トラブルシューティング
Attach fails
確認項目- Check private reachability.
- Verify the node token and version.
- Confirm the role and current membership.
Correct trust or network prerequisites before repeating the attach action.