Hi, 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 https://stackoverflow.com/questions/6676972/moving-a-shard-from-one-bigcouch-server-to-another-for-balancing 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 <[email protected]> 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: > > http://docs.couchdb.org/en/2.0.0/cluster/sharding.html > > https://medium.com/linagora-engineering/setting-up-a-couchdb-2-cluster-on-centos-7-8cbf32ae619f > > 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] <http://www.cabify.com/> > > *Carlos Alonso* > Data Engineer > Madrid, Spain > > [email protected] > > Prueba gratis con este código > #CARLOSA6319 <https://cabify.com/i/carlosa6319> > [image: Facebook] <http://cbify.com/fb_ES>[image: Twitter] > <http://cbify.com/tw_ES>[image: Instagram] <http://cbify.com/in_ES>[image: > Linkedin] <https://www.linkedin.com/in/mrcalonso> > > -- > 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.
