Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify process of renaming a node prior to cluster join #1022

Open
mkleins opened this issue Nov 27, 2017 · 1 comment
Open

Simplify process of renaming a node prior to cluster join #1022

mkleins opened this issue Nov 27, 2017 · 1 comment

Comments

@mkleins
Copy link

mkleins commented Nov 27, 2017

I tried to create a cluster with an automation tool (not manually)

Current Behavior

When i install couchDB in cluster mode, its mandorty to change default node name ([email protected]) by FDQN in vm.args file. In this case, couchDB create a new node and keeps the first node active ([email protected]).
To make the cluster work, i need to delete the first node. Not nice if i want to use an automation system like ansible.

Possible Solution

When renaming node, replace the node name without adding a new one.

Steps to Reproduce (for bugs)

  1. Install couchDB with repositories (Debian)
  2. Rename node in vm.args file
  3. Restart couchDB daemon
  4. View nodes in _membership URL

Your Environment

Tried on Debian 9 with CouchDB 2.1.1

@wohali
Copy link
Member

wohali commented Jan 16, 2018

This isn't really a packaging problem, it's CouchDB overall. If you install CouchDB from source, then run it, then go to change the node name and restart it, you'll have the same problem. You then need to DELETE the no-longer existing node.

In Debian, the vm.args file is considered a conffile. Have you tried placing a /opt/couchdb/etc/vm.args file down first, then installing the package?

@wohali wohali changed the title Cluster's installation with automation tools Simplify process of renaming a node prior to cluster join Jan 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants