Couchbase VDBs can span multiple nodes for distributed cluster configurations. Multi-node VDBs provide better performance and fault tolerance.
Before you begin
-
Multiple target environments are available
-
All target hosts have identical Couchbase version installed
-
Network connectivity between nodes is available
Limitations
-
Child VDBs cannot be provisioned from multi-node VDBs
-
Multi-node VDBs cannot be cloned
-
Maximum 9 nodes supported (Couchbase cluster limitation)
Procedure
Follow the single-node procedure, then during the cluster configuration step:
-
On the Additional Nodes section, select + Add Node for each additional node.
-
For each additional node, configure:
-
Environment – Target environment where this node will run
-
Environment User – OS user with Couchbase privileges on that host
-
Host/IP – Network address for cluster communication (FQDN recommended)
-
Services – Which Couchbase services run on this node (Data, Index, Query, Search, Analytics, Eventing)
-
-
Repeat for each additional node up to maximum 9 nodes.
Result
A distributed Couchbase cluster is provisioned with data distributed across multiple nodes. The cluster automatically balances load and provides redundancy.
If provisioning fails
If VDB provisioning encounters errors:
-
Version mismatch – Verify target Couchbase version matches source exactly
-
Port conflicts – Confirm target ports 8091 (management) and 11210 (data/KV) are available
-
Insufficient disk space – Ensure target mount path has enough free space for VDB
-
SSH access issues – Test SSH connectivity to target host
-
expect utility missing – Verify expect is installed on target host
-
Mount path inaccessible – Confirm mount path exists and is writable by environment user
Review Continuous Data Engine logs and Couchbase instance logs at /opt/couchbase/var/lib/couchbase/logs for detailed error messages.