wohali commented on a change in pull request #326: Split of Firewall and Erlang Configuration URL: https://github.com/apache/couchdb-documentation/pull/326#discussion_r224876316
########## File path: src/cluster/setup.rst ########## @@ -45,6 +45,28 @@ possible to force an Erlang application to use a specific port rage. This documentation will use the range TCP ``9100-9200``. Open up those ports in your firewalls and it is time to test it. +Configure and Test the Communication with Erlang +================================================ + +Make CouchDB use correct IP|FQDN and the open ports. +---------------------------------------------------- + +In file ``etc/vm.args`` change the line ``-name [email protected]`` to +``-name couchdb@<this-nodes-ip-address|FQDN>`` which defines the name of the node. +For clustered setup, each node in system must have a unique name. Can also be a Review comment: Almost right... Each node must have an identifier that allows remote systems to talk to it. The node name is of the form `name@<public-ip-address|fully-qualified-domain-name>`. The `name` portion can be `couchdb` on all nodes, _unless_ you are running more than 1 CouchDB node on the same server with the same IP address or domain name. In that case, we recommend `names` of `couchdb1`, `couchdb2`, etc. The second portion of the node name must be an identifier by which other nodes can access this node -- either the node's fully qualified domain name (FQDN) or the node's IP address. The FQDN is preferred so that you can renumber the node without disruption to the cluster. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
