media server logo
Guía del producto

Nodos de clúster

Register and manage trusted master or slave nodes for supported self-hosted cluster membership.

Dónde encontrarlo en CallabaAdvanced → Cluster nodes
Qué hace este módulo

Cluster nodes manage database and application membership. They do not promise automatic workload scheduling, geographic routing or seamless autoscaling.

Antes de empezar

  • Private network reachability between nodes.

  • Administrator API token for the node being attached.

  • Compatible Callaba versions and a current configuration backup.

Ajustes explicados

Se explican los controles que necesita el operador. Los nombres internos y eventos de implementación se omiten intencionadamente.

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.

Primer flujo seguro

  1. 01

    Back up the current configuration and verify private network connectivity.

  2. 02

    Create the node with its intended role, private host and administrator token.

  3. 03

    Attach the node and wait for membership to settle.

  4. 04

    Start it and verify reachability plus the expected database membership.

  5. 05

    Test detach and recovery procedure outside a production incident.

Ejemplos de flujo

Úsalo cuando

Add a trusted slave node

A self-hosted deployment needs a supported additional cluster member.

Primary nodeCurrent cluster
Private networkReachability
Slave nodeAttach + start
MembershipVerified state
Diagrama animado del flujo: Add a trusted slave node

Cómo construirlo

  1. 1

    Confirm compatible versions, backup and private connectivity.

  2. 2

    Register the Slave with its private host and token.

  3. 3

    Attach and start the node in a controlled window.

  4. 4

    Verify node state and database membership before using it operationally.

Verificar el resultado

  • 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.

Solución de problemas

Attach fails

Comprobar
  • Check private reachability.
  • Verify the node token and version.
  • Confirm the role and current membership.
Después, haz esto

Correct trust or network prerequisites before repeating the attach action.