couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: CouchDB 2.0 Clustering
Date Fri, 26 May 2017 17:42:42 GMT

That's expected behaviour. Existing databases are not rebalanced as new nodes are added. New
databases are distributed over them, of course, up to the limit of q and n parameters. 

I wrote a guide a while back for shard moves at
and it still holds

Future releases of couchdb should make this easier. 

Sent from a camp site with surprisingly good 4G signal 

> On 26 May 2017, at 16:24, Carlos Alonso <> wrote:
> Hi guys!
> I'm very new to CouchDB administration and I was trying to setup a cluster
> and do basic operations on it (adding nodes, moving shards, ...) following
> this two resources:
> So far I've managed to setup a cluster and add nodes to it, but newly added
> nodes (once the cluster is running) have not received any shard from
> _global_changes, _metadata, _replicator and _users databases.
> I was wondering if it makes sense to have a copy on each node of those
> databases to have them homogeneous (nodes added to the cluster when the
> cluster was created all received their copy).
> Thanks in advance!
> -- 
> [image: Cabify - Your private Driver] <>
> *Carlos Alonso*
> Data Engineer
> Madrid, Spain
> Prueba gratis con este código
> #CARLOSA6319 <>
> [image: Facebook] <>[image: Twitter]
> <>[image: Instagram] <>[image:
> Linkedin] <>
> -- 
> Este mensaje y cualquier archivo adjunto va dirigido exclusivamente a su 
> destinatario, pudiendo contener información confidencial sometida a secreto 
> profesional. No está permitida su reproducción o distribución sin la 
> autorización expresa de Cabify. Si usted no es el destinatario final por 
> favor elimínelo e infórmenos por esta vía. 
> This message and any attached file are intended exclusively for the 
> addressee, and it may be confidential. You are not allowed to copy or 
> disclose it without Cabify's prior written authorization. If you are not 
> the intended recipient please delete it from your system and notify us by 
> e-mail.

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message