Suggested minor enhancement to allow multiple instances of ElasticSearch #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Suggested minor enhancement to allow multiple instances of ElasticSearch one one machine/VM, as I mentioned yesterday.
To invoke the enhancement either set ES_NUM_NODES (to the number of nodes), ES_MULTI_CLUSTER (to the cluster name to check automatically, see below), either in /etc/sysconfig/elasticsearch (should put commented out sets for these as 1/elasticsearch in that file - I can fork that and do if you want to use this enhancement), or from the command line, eg "ES_MULTI_CLUSTER=elasticsearch /etc/init.d/elasticsearch start", or "ES_NUM_NODES=2 /etc/init.d/elasticsearch start".
If a cluster name is specified, the number of nodes is set to the number of subdirectories of ES_PATH_DATA//nodes.
For status/stop, setting the variables is not mandatory - the script will try to work out what's going on itself.