The Cluster / High Availability feature allows OneDB to operate with multiple nodes to improve service availability and reduce the risk of downtime. By adding cluster nodes, OneDB can distribute and synchronize important system configurations across available nodes, helping the platform remain operational even when one node requires maintenance or experiences an issue.

This feature is useful for production environments where OneDB is expected to serve database security traffic continuously.

Overview

OneDB Cluster is designed to support a high availability deployment model. Each node in the cluster can participate as part of the OneDB environment and help maintain system continuity.

From the Cluster / High Availability page, administrators can:

• Add a new OneDB node to the cluster.
• View registered cluster nodes.
• Monitor the current status of each node.
• Check the last heartbeat received from each node.
• Manage available cluster node actions.

Cluster Size

OneDB Cluster supports multiple nodes for high availability deployments. The number of nodes that can be added may depend on the active license tier, deployment package, and infrastructure capacity.

Some license tiers may define a specific maximum number of cluster nodes, while strategic or large-scale deployments may support a hardware-bound cluster size depending on the agreed deployment design.

For best results, all cluster nodes should use the same OneDB version and compatible database schema.

Add Cluster Node

To add a new node, enter the target node IP address in the Node IP field and click Add Node.

Example:

192.168.1.100

After the node is submitted, OneDB will attempt to initialize the node and register it into the cluster.

If the node can be reached and initialized successfully, it will be added to the cluster node list.

Cluster Nodes

The Cluster Nodes section displays the list of nodes currently registered in the OneDB cluster.

The table provides the following information:

Node Heartbeat

OneDB uses heartbeat information to help determine whether a cluster node is still reachable.

The Last Heartbeat column shows the latest communication timestamp from the node. If the heartbeat is not updated for a certain period, the node may be unreachable or not functioning properly.

Administrators should check network connectivity, service status, and firewall rules if a node stops sending heartbeat updates.

Failed Node Initialization

If OneDB cannot initialize a node, an error message will be displayed.

Example:

Failed to initialize cluster node 192.168.1.100

This usually means OneDB could not connect to the target node or the target node is not ready to join the cluster.

Common causes include:

• The target node is offline.
• The IP address is incorrect.
• Required OneDB services are not running on the target node.
• Network connectivity between nodes is blocked.
• Firewall rules do not allow communication between OneDB nodes.
• The target node has not been prepared with the required OneDB installation.

Recommended Checks

Before adding a node to the cluster, ensure that:

• The target server is reachable from the current OneDB node.
• OneDB is installed and running on the target node.
• Required network ports are open between cluster nodes.
• The node IP address is correct.
• The target node is intended to be part of the same OneDB deployment environment.

Best Practice

For production environments, deploy OneDB cluster nodes on separate servers or virtual machines. This helps reduce the impact of infrastructure failure and improves overall service availability.

For best results, all cluster nodes should use the same OneDB version and a compatible database schema. This helps prevent synchronization issues and ensures consistent behavior across nodes.

It is also recommended to monitor node status regularly and verify that heartbeat information is updated correctly.

Summary

The Cluster / High Availability feature helps OneDB run in a more resilient deployment model by allowing multiple nodes to participate in the same environment. Administrators can add nodes, monitor their status, and verify node availability through heartbeat information.

This feature is especially useful for production deployments that require higher uptime and better operational continuity.