You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/06/25 18:13:08 UTC

[GitHub] [couchdb] wohali commented on issue #2140: Cluster does not recover from temporary network partition

wohali commented on issue #2140:
URL: https://github.com/apache/couchdb/issues/2140#issuecomment-649738969


   @rwpfeifer I'm sorry that we don't have any more information to provide here. The only thing I can think of is that if you are actually tearing down the network interface itself, that `epmd` - the Erlang Port Mapper Daemon - may be losing the interface it's bound to. This, in turn, would prevent other nodes from reaching CouchDB on that node, since they can't talk to `epmd`, which is how they find out how to talk to CouchDB on e.g. port `9100/tcp`.
   
   When you kill CouchDB, `epmd` will also terminate. Restarting CouchDB will then automatically restart `epmd`.
   
   No Erlang distributed process can survive epmd being restarted from underneath it, to my knowledge, so the only workaround for you would be to ensure that when you interrupt networking, you do not also tear down the virtual interface in the VM guest at the same time.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org