That's brilliant. I just wanted to be able to start CouchDB 2.0 in
single node mode on a laptop.
So, I changed -name couchdb to -name [email protected] in vm.args.
I then deleted my _metadata db and the metadata shards manually, got rid
of the [email protected] in 127.0.0.1:5986/_nodes, replaced
[email protected] by [email protected] in all _dbs documents
and recreated the _metadata db.
It works great.
That was actually the last piece missing for being able to embed couchdb
in my OS X app.
Thanks a lot,
Antoine
Adam Kocoloski <mailto:[email protected]>
19 août 2015 00:18
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
Antoine Duchâteau <mailto:[email protected]>
18 août 2015 11:39
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
