haproxy) to scale CouchDB out horizontally. More details of the clustering feature are available in the Cluster Reference.
sorted=false) for a performance boost.
/_bulk_getspeeds up the replication protocol over low-latency connections
/_node/api to access individual nodes’ configuration and compaction features
/_cluster_setupapi to set up a cluster from scratch.
/_upapi to signal health of a node to a load-balancer
_dbsdatabases visible only through this interface.
replicator/dbconfig option has been removed. Instead
_replicatorand any database names ending with the
/_replicatorsuffix will be recognized as replicator databases by the system.
202when storing a document.
all_or_nothingis no longer supported by the bulk_docs API
All known issues filed against the 2.0 release are contained within the official CouchDB JIRA instance.
The following are some highlights of known issues for which fixes did not land in time for the 2.0.0 release:
COUCHDB-2980: The replicator (whether invoked via
_replicate or a
document stored in the
_replicator database) understands two kinds of
source and target:
https://foo:firstname.lastname@example.org/db1), called a “remote” source or target
db1), called a “local” source or target.
Whenever the latter type is used, this refers to a local unclustered database, not a clustered one.
In a future release we hope to support “local” source or target specs to clustered databases. For now, we recommend always using the URL format for both source and target specifications.
COUCHDB-3034: CouchDB will occasionally return 500 errors when multiple clients attempt to PUT or DELETE the same database concurrently.
COUCHDB-3119: Adding nodes to a cluster fails if the Erlang node name
couchdb (of the form
COUCHDB-3050: Occasionally the
dev/run script used for development
purposes to start a local 3-node cluster will fail to start one or more
COUCHDB-2817: The compaction daemon will only compact views for shards that contain the design document.
COUCHDB-2804: The fast_view optimization is not enabled on the clustered interface.