Good question. The node name is set by the vm.args file. It defaults to “-name couchdb” which will cause CouchDB to try to discover the system hostname, but you could set that value directly as “-name couchdb@<FQDN>” or even “-name couchdb@<IPV4>”. The key point is to set it to something that can be routed from other nodes if you ever plan to exercise the clustering capability.
Does that make sense? Cheers, Adam > On Aug 18, 2015, at 5:39 AM, Antoine Duchâteau <aduch...@gmail.com> wrote: > > Hi list, > > I've got the following problem with CouchDB 2.0 > > If I create a database when the computer has one hostname and subsequently > start the database again when the hostname is different, the database exposed > on 5984 appears empty because there is a mismatch in the node name and fabric > does not find the shards anymore. > > What is the best way to handle this situation ? > I tried using hostname to force the hostname before launching couchdb but it > only works if I first disconnect all network connections... Which is not > really acceptable. > > Is there a way to force the hostname CouchDB is going to use ? > > Thanks in advance, > Antoine > > -- > *Antoine Duchâteau* > Managing Director > Email : a...@taktik.be <mailto:a...@taktik.be> > GSM : +32 499 534 536 > > _______________ > *TAKTIK SA* > Parc de l'Alliance > Avenue de Finlande 8 > 1420 Braine l'Alleud > Tel : +32 2 333.58.40 > <http://www.taktik.be/>http://www.taktik.be >
