[
https://issues.apache.org/jira/browse/COUCHDB-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035912#comment-16035912
]
ASF subversion and git services commented on COUCHDB-3119:
----------------------------------------------------------
Commit d75693ea94de8595b69fcf8e9eb189664e115574 in couchdb-setup's branch
refs/heads/master from [~adrienverge]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-setup.git;h=d75693e ]
add_node: Don't fail if node name != "couchdb" or "node1"
Adding nodes to a cluster fails if the node names (the `name` of
`name@hostname` in vm.args) is different from "couchdb".
The code currently infers this name from the port: "node1" if 15984,
"node2" if 25984, "node3" if 35984, "couchdb" otherwise. No other
possibility.
This is not suited for a production set-up, where multiple servers could
have different names.
This patch fixes this problem by adding an optional "name" option to the
"add_node" command:
POST /_cluster_setup
{
"action": "add_node",
"username": "root",
"password": "******",
"host": "production-server.com",
"port": 5984,
"name": "node5"
}
This fixes: COUCHDB-3119
> Cluster setup: `add_node` fails if node name != "couchdb"
> ---------------------------------------------------------
>
> Key: COUCHDB-3119
> URL: https://issues.apache.org/jira/browse/COUCHDB-3119
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Adrien Vergé
>
> Adding nodes to a cluster fails if the node names (the `name` of
> `name@hostname` in vm.args) is different from "couchdb". The code currently
> infers this name from the port: "node1" if 15984, "node2" if 25984, "node3"
> if 35984, "couchdb" otherwise. No other possibility.
> This is not suited for a production set-up, where multiple servers could have
> different names.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
