[NOT MAINTAINED]
Create an ElasticSearch cluster with a single bash command :
vagrant up
Programs, plugins, libs and versions information
| Program, plugin, lib | Version | How to use it |
|---|---|---|
| ElasticSearch | 1.4.3 | http://www.elasticsearch.org/guide/ |
| Java (openjdk-7-jre) | 1.7.0_25 | |
| elasticsearch-image | 1.2.0 | https://github.com/kzwang/elasticsearch-image |
| elasticsearch-mapper-attachments | 2.4.2 | https://github.com/elasticsearch/elasticsearch-mapper-attachments |
| rssriver (david pilato) | 1.3.0 | http://www.pilato.fr/rssriver/ |
| elasticsearch-river-jdbc | 1.4.0.9 | https://github.com/jprante/elasticsearch-river-jdbc |
| elasticsearch-river-rabbitmq | 2.4.1 | https://github.com/elasticsearch/elasticsearch-river-rabbitmq |
| elasticsearch-river-twitter | 2.4.2 | https://github.com/elasticsearch/elasticsearch-river-twitter |
| elasticsearch-river-wikipedia | 2.4.1 | https://github.com/elasticsearch/elasticsearch-river-wikipedia |
This plugins are just installed through the bin/plugin -i command. You must configure everything else.
Cluster default configuration
| Configuration | Value(s) |
|---|---|
| Cluster name | elasticsearch-cluster-test |
| Nodes names | thor, zeus, isis, baal, shifu |
| VM names | vm1, vm2, vm3, vm4, vm5 |
| Default cluster network IP | 10.0.0.0 |
Must have on your local machine
- VirtualBox (last version)
- Vagrant (>=1.5)
- cUrl (or another REST client to talk to ES)
Clone this repository
git clone [email protected]:ypereirareis/vagrant-elasticsearch-cluster.git
WARNING
You'll need enough RAM to run VMs in your cluster. Each new VM launched within your cluster will have 512M of RAM allocated. You can change this configuration in the Vagrantfile once cloned.
Important
The maximum number VMs running in the cluster is 5. Indeed, it is possible to run much more than 5, but it's not really needed for a test environment cluster, and the RAM needed would be much more important. If you still want to use more than 5 VMs, you will have to add/edit your own configuration files in the conf directory.
Run the cluster
Simply go in the cloned directory (vagrant-elasticsearch-cluster by default). Execute this command :
vagrant up
By default, this command will boot 5 VMs, with My amazing ES cluster name, 512M of RAM for each node and this network ip address 10.0.0.0.
You can change the cluster size with the CLUSTER_COUNT variable:
CLUSTER_COUNT=3 vagrant up
You can change the cluster name with the CLUSTER_NAME variable:
CLUSTER_NAME='My awesome cluster' vagrant up
You can change the cluster RAM used for each node with the CLUSTER_RAM variable:
CLUSTER_RAM=1024 vagrant up
You can change the cluster network IP address with the CLUSTER_IP_PATTERN variable:
CLUSTER_IP_PATTERN='172.16.15.%d' vagrant up
Providing the CLUSTER_NAME, CLUSTER_COUNT, CLUSTER_RAM, CLUSTER_IP_PATTERN variables is only required when you first start the cluster.
Vagrant will save/cache these values so you can run other commands without repeating yourself.
Of course you can use all these variables at the same time :
$ CLUSTER_NAME='My awesome search engine' CLUSTER_IP_PATTERN='172.16.25.%d' CLUSTER_COUNT=3 CLUSTER_RAM=512 vagrant status
----------------------------------------------------------
Your ES cluster configurations
----------------------------------------------------------
Cluster Name: My awesome search engine
Cluster size: 3
Cluster network IP: 172.16.25.0
Cluster RAM (for each node): 512
----------------------------------------------------------
----------------------------------------------------------
Current machine states:
vm1 not created (virtualbox)
vm2 not created (virtualbox)
vm3 not created (virtualbox)
...
The names of the VMs will follow the following pattern: vm[0-9]+.
The trailing number represents the index of the VM, starting at 1.
ElasticSearch instance is started during provisioning of the VM. The command is launched into a new screen as root user inside the vagrant.
Once the cluster is launched (please wait a few seconds) go to : http://10.0.0.11:9200
Plugins URLs (replace IP if you changed it with CLUSTER_IP_PATTERN var) :
- http://10.0.0.11:9200/_plugin/marvel
- http://10.0.0.11:9200/_plugin/paramedic/
- http://10.0.0.11:9200/_plugin/head/
- http://10.0.0.11:9200/_plugin/bigdesk
- http://10.0.0.11:9200/_plugin/HQ/
The default configuration (HTTP enabled for all nodes) allows you to use any of your VM IPs. If one (or more) of your nodes fails, try with another IP to see what happened.
By default the cluster nodes have an IP following the pattern "10.0.0.%d" as you can see in Vagrantfile.
But you can change it using an ENV var :
CLUSTER_COUNT=2 CLUSTER_IP_PATTERN='172.16.10.%d' vagrant up
- This command will start 2 ES instances with IPs like : 172.16.10.11, 172.16.10.12.
⚠️ Before that, you must verify that config files (conf/vm*) do not exist or delete them.- Indeed, this files need to be re-written.
You will see this kind of shell :
$ CLUSTER_COUNT=2 CLUSTER_IP_PATTERN='172.16.10.%d' vagrant up
Cluster size: 2
Cluster IP: 172.16.10.0
Bringing machine 'vm1' up with 'virtualbox' provider...
Bringing machine 'vm2' up with 'virtualbox' provider...
And you now access to nodes like that : http://172.16.10.11:9200
Stop the cluster
vagrant halt
This will stop the whole cluster. If you want to only stop one VM, you can use:
vagrant halt vm2
This will stop the vm2 instance.
Destroy the cluster
vagrant destroy
This will stop the whole cluster. If you want to only stop one VM, you can use:
vagrant destroy vm2
Remove the cluster
vagrant box remove ypereirareis/debian-elasticsearch-amd64
This will remove your local copy of the vagrant base-box.
Managing ElasticSearch instances
Each VM has its own ElasticSearch instance running in a screen session named elastic.
Once connected to the VM, you can manage this instance with the following commands:
(sudo) node-start: starts the ES instance(sudo) node-stop: stops the ES instance(sudo) node-restart: restarts the ES instance(sudo) node-status: displays ES instance's status(sudo) node-attach: bring you to the screen session hosting the ES instance. Use^Adto detach.
You should be brought to the screen session hosting ElasticSearch and see its log.
The first launch of ES instance is done by vagrant provisionning.
So you should prepend sudo for each command above.
But you have the possibility to start an ES instance as 'vagrant' user from the VM.
vagrant ssh vmX
sudo node-stop
node-start
This chain of commands will log you into a chosen VM, will stop the ES 'root-user' instance and will start a 'vagrant-user' ES instance.
If you need or want to change the default working configuration of your cluster, you can do it adding/editing elasticsearch.yml files in conf/vmX/elasticsearch.yml. Each node configuration is shared with VM thanks to this "conf" directory.
By default, this configuration files are auto-generated by Vagrant when running the cluster for the first time. In this case, default values listed at the top of this page are used.
- elasticsearch-head - https://github.com/mobz/elasticsearch-head
- elasticsearch-paramedic - https://github.com/karmi/elasticsearch-paramedic
- BigDesk - https://github.com/lukas-vlcek/bigdesk
- Marvel - http://www.elasticsearch.org/overview/marvel/
- ElasticsearchHQ - http://www.elastichq.org/
Create a "subscriptions" index with 5 shards and 2 replicas
curl -XPUT 'http://10.0.0.11:9200/subscriptions/' -d '{
"settings" : {
"number_of_shards" : 5,
"number_of_replicas" : 2
}
}'
Index a "subscription" document inside the "subscriptions" index
curl -XPUT 'http://10.0.0.11:9200/subscriptions/subscription/1' -d '{
"user" : "ypereirareis",
"post_date" : "2014-03-26T14:12:12",
"message" : "Trying out vagrant elasticsearch cluster"
}'
You can now perform any action/request authorized by elasticsearch API (index, get, delete, bulk,...)
You can use every vagrant command to manage your cluster and VMs. This project is simply made to launch a working ES cluster with a single command, using vagrant/virtualbox virtual machines.
Use it to test every configuration/queries you want (split brain, unicast, recovery, indexing, sharding)
Do forks, PR, and MRs !!!!
- Add extra plugins or applications in the base box (redis, logstash, kibana, ...)
- Add some configurations to illustrate split brain, unicast discovery, load balancing, snapshots, recovery...
- Add possibility to configure cluster name, RAM per node AND hostnames through the shell (ENV vars)
The MIT License (MIT)
Copyright (c) 2017 Yannick Pereira-Reis
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.