Hi guys. I've been experimenting with operating a CouchDB 2.0 cluster and I've seen the following unexpected behaviour.
Having a db with just one shard and just one repica, and a client that just inserts a new document and reads /db/_all_docs on a loop every second (just to simulate a controlled load) I expect the number of docs on every read to be sequentially incrementing, and it actually is. However, at some point I add a new replica for that shard, in a different node of the cluster and, while the newly added node is synchronising its shard the number of read documents is not incremented anymore!! It is only when the new repica is synchronised that the numbers match again. It feels like while replicating those requests using the new replica as coordinator are resolved locally instead of via quorum as I'd expect. Has anyone seen something similar? -- [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.
