# 4. Cluster Management

As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:

  - Standalone: In this mode, CouchDB’s clustering is unavailable. CouchDB’s HTTP-based replication with other CouchDB installations remains available.

  - Cluster: A cluster of CouchDB installations internally replicate with each other via optimized network connections. This is intended to be used with servers that are in the same data center. This allows for database sharding to improve performance.

This section details the theory behind CouchDB clusters, and provides specific operational instructions on node, database and shard management.

- 4.1. Theory
- 4.2. Node Management
  - 4.2.1. Adding a node
  - 4.2.2. Removing a node
- 4.3. Database Management
  - 4.3.1. Creating a database
  - 4.3.2. Deleting a database
  - 4.3.3. Placing a database on specific nodes
- 4.4. Shard Management
  - 4.4.1. Introduction
  - 4.4.2. Examining database shards
  - 4.4.3. Moving a shard
  - 4.4.4. Specifying database placement
  - 4.4.5. Splitting Shards
  - 4.4.6. Stopping Resharding Jobs
  - 4.4.7. Merging Shards
- 4.5. Clustered Purge
  - 4.5.1. Internal Structures
  - 4.5.2. Compaction of Purges
  - 4.5.3. Local Purge Checkpoint Documents
  - 4.5.4. Internal Replication
  - 4.5.5. Indexes
  - 4.5.6. Config Settings
- 4.6. TLS Erlang Distribution
  - 4.6.1. Generate Certificate
  - 4.6.2. Config Settings
  - 4.6.3. Connect to Remsh
- 4.7. Troubleshooting CouchDB 3 with WeatherReport
  - 4.7.1. Overview
  - 4.7.2. Usage