Re: CouchDB 2.0 cluster problem when first node is down

would be useful to get the response to GET :5984/_membership from both nodes during this period. B. > On 6 May 2016, at 23:33, Jan Lehnardt wrote: > > Oleg, thanks for the report! This was reported before, but only very > recently and we are still looking into it. Can you

Re: CouchDB 2.0 cluster problem when first node is down

Oleg, thanks for the report! This was reported before, but only very recently and we are still looking into it. Can you maybe add your setup details to the ticket at: https://issues.apache.org/jira/browse/COUCHDB-3009? Thank you! Best Jan -- > On 06 May 2016, at 20:18, Oleg Cohen

CouchDB 2.0 cluster problem when first node is down

Greetings, We ran into an issue when testing CouchDB 2.0 clustering. We ran a 2-node cluster using the dev/run -n 2 command. If we bring node2 down, all on node1 is still working fine. When we bring down node1 using remsh and issuing init:stop(). command, the databases on node2 are no longer