Cluster Operations

Cluster Operations

Cluster operations include starting, stopping, adding nodes, and removing the server from the cluster.

Warning: Never stop or restart Couchbase Server before you first remove that node from a cluster.

The Servers menu indicates overall server information for the cluster. Click the server name (IP address) to view the server details such as uptime, operating system, Couchbase Server version, data storage path, and Index Storage path.

  • To search through the server list, click Filter and enter the server name in the field.
  • To manage server groups, click Groups. For more information, see Manage Server Groups.
  • To add a new server, click Add Server. For more information, see Adding a Node.

Table 1. Server Details
Field Description
name / group The server IP address and the group name this server belongs to.
services The running services on this server. The options are data, full text, index, and query.
CPU The CPU usage on this server.
RAM The total RAM on this server.
swap The swap information on this server.
disk used The total disk space used on this server.
items The number of items processed on this server.
Statistics Click Statistics link to view stats details on this server. For more information, see Monitoring Statistics.


Couchbase Server specifies limits and limitations that may affect server usage and implementation. Depending on the size of the documents passed to the view engine, the performance of Couchbase Server may be affected.
Limit Default Value Description
Max key length 250 bytes The maximum length of the document ID (key).
Max value size 20 MB The maximum size of the JSON document.
Max buckets per cluster 10 The maximum number of buckets in a cluster. See section for information on how to update the maximum number of buckets in a cluster.
Max view key size 4096 bytes The maximum size of the key (first attribute) in the emit() function.
Max doc size for indexing 20 MB The maximum size of a document that can be indexed. The default value is set to 20 MB to ensure that all documents get indexed.

In Couchbase Server version 2.x and earlier, the view engine enforced a limit of 1MB on documents that can be indexed. As a result, when the size of a document exceeded the limit, the view engine (in version 2.x) did not index that document.

Max key-value size per document 1 MB The maximum byte size allowed to be emitted for a single document and per view. This value is the sum of the sizes of all emitted keys and values.

If a document emits a key-value pair that exceeds the specified maximum key-value size per document, an error is logged and that document is not indexed.

Function timeout 1000 ms The maximum duration (in milliseconds) to execute all the MapReduce functions in a design document against a single document (map function) or against a list of map values or reductions (reduce or rereduce function). If the execution time for a document exceeds the specified value, the execution is aborted and that document is not indexed.
Sub-document path length 1024 bytes The maximum length of a sub-document path that may be used in one of the sub-document operations.
Sub-document path nesting level 32 The maximum number of levels a path may reference in sub-document operations.