renaming and removal of nodes causes bigcouch replication not to work
It seems that the recent removal of some nodes in bitmask, and then adding new ones, causes the bigcouch situatioin to totally freak out.
What we did in bitmask was to do the following: remove mole and replace it with clam remove python and replace it with urchin
Each of these was and is a couchdb instance. The bigcouch replication nodes were not connected. after fighting for a while I ended up finding out that the bigcouch nodes were not connected:
root@urchin:~# /usr/bin/curl --netrc-file /etc/couchdb/couchdb.netrc -X GET 'http://127.0.0.1:5986/nodes/_all_docs' {"total_rows":1,"offset":0,"rows":[ {"id":"bigcouch@urchin.dev.bitmask.net","key":"bigcouch@urchin.dev.bitmask.net","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}} ]}
and I had to manually connect them:
root@urchin:~# /usr/bin/curl --netrc-file /etc/couchdb/couchdb.netrc -X PUT 'http://127.0.0.1:5986/nodes/bigcouch@clam.dev.bitmask.net' -d {} {"ok":true,"id":"bigcouch@clam.dev.bitmask.net","rev":"1-967a00dff5e02add41819138abb3284d"} root@urchin:~# /usr/bin/curl --netrc-file /etc/couchdb/couchdb.netrc -X GET 'http://127.0.0.1:5986/nodes/_all_docs' {"total_rows":2,"offset":0,"rows":[ {"id":"bigcouch@clam.dev.bitmask.net","key":"bigcouch@clam.dev.bitmask.net","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}}, {"id":"bigcouch@urchin.dev.bitmask.net","key":"bigcouch@urchin.dev.bitmask.net","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}} ]}
this should be happening automatically
(from redmine: created on 2013-05-22, closed on 2013-05-23, relates #2659 (closed), relates #3049)