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 2019/06/15 11:37:20 UTC

[GitHub] [couchdb] raoyitao opened a new issue #2054: [CouchDB 2.3.1] Cluster setup timed out waiting for nodes to connect

raoyitao opened a new issue #2054: [CouchDB 2.3.1] Cluster setup timed out waiting for nodes to connect
URL: https://github.com/apache/couchdb/issues/2054
 
 
   I have 3 hosts, on each there is a CouchDB 2.3.1 running, but I cannot join them as a cluster, I got the error "Cluster setup timed out waiting for nodes to connect", I search through Google but there's not hint why this happen.
   
   ## Description
   
   I have configure **vm.args**, adding following content:
   
   **-name couchdb@<[abc].mydoman.com>
   -setcookie brum_brum
   -kernel inet_dist_listen_min 9100
   -kernel inet_dist_listen_max 9110**
   
   The 3 hosts are **a.mydomain.com**, **b.mydomain.com**, **c.mydomain.com**, they can ping each other smoothly. In local.ini config files, the same **port**, **uuid** and **admin/password** were set.
   
   Then I can run CouchDB on these hosts:
   > **COUCHDB_ARGS_FILE=/path/to/my/vm.args ./bin/couchdb**
   
   I also run this command on another host to test connections:
   
   > **erl -name couchdb@d.mydomain.com -setcookie 'brum_brum' -kernel inet_dist_listen_min 9100 -kernel inet_dist_listen_max 9110**
   (couchdb@d.mydomain.com)> **net_kernel:connect_node('couchdb@a.mydomain.com').**
   **true**
   
   It shows all these nodes can be connected.
   
   ## Steps to Reproduce
   
   I follow the official document to setup a cluster, with the command for each node:
   **curl -X POST -H "Content-Type: application/json" http://admin:pass@<IP-ADDR>:<PORT>/_cluster_setup -d '{"action": "enable_cluster", "bind_address": "0.0.0.0", "username": "admin", "password": "pass", "node_count": "3"}'**
   
   Then choose a coordination node and run these commands for the other two:
   **curl -X POST -H "Content-Type: application/json" http://admin:pass@<COORD-IP>:<PORT>/_cluster_setup -d '{"action": "enable_cluster", "bind_address": "0.0.0.0", "username": "admin", "password": "pass", "port": <PORT>, "node_count": "3", "remote_node": "<REMOTE-IP>", "remote_current_user": "admin", "remote_current_password": "pass"}'**
   **curl -X POST -H "Content-Type: application/json" http://admin:pass@<COORD-IP>:<PORT>/_cluster_setup -d '{"action": "add_node", "host": "<REMOTE-IP>", "port": <PORT>, "username": "admin", "password": "pass"}'**
   
   At last finishe cluster setup:
   **curl -X POST -H "Content-Type: application/json" http://admin:pass@<COORD-IP>:<PORT>/_cluster_setup -d '{"action": "finish_cluster"}'**
   
   But unfortunately I got the error after a few seconds:
   **{"error":"setup_error","reason":"Cluster setup timed out waiting for nodes to connect"}**
   
   The status of CouchDB cluster:
   > **curl http://admin:pass@<COORD-IP>:<PORT>/_cluster_setup**
   **{"state":"cluster_enabled"}**
   
   ## My Environment
   
   * CouchDB Version used: **2.3.1 extracted from el7 RPM package**
   * Operating System and version: **Red Hat Enterprise Linux Server release 6.10**
   
   ## Additional context
   
   I have ever set 3 CouchDB servers as a cluster, but the version I used is 2.3.0. And now I switch to 2.3.1 seems I cannot setup cluster. I don't know why there is a timeout message.

----------------------------------------------------------------
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


With regards,
Apache Git Services