Running Elasticsearch

Elasticsearch is now ready to run. To start it up in the foreground:

cd elasticsearch-<version>

Add -d if you want to run it in the background as a daemon.

If you’re running Elasticsearch on Windows, simply run bin\elasticsearch.bat instead.

Test it out by opening another terminal window and running the following:

curl 'http://localhost:9200/?pretty'

If you’re running Elasticsearch on Windows, you can download cURL from cURL provides a convenient way to submit requests to Elasticsearch and installing cURL enables you to copy and paste many of the examples in this book to try them out.

You should see a response like this:

   "status": 200,
   "name": "Shrunken Bones",
   "version": {
      "number": "1.4.0",
      "lucene_version": "4.10"
   "tagline": "You Know, for Search"

This means that your Elasticsearch cluster is up and running, and we can start experimenting with it.

A node is a running instance of Elasticsearch. A cluster is a group of nodes with the same that are working together to share data and to provide failover and scale, although a single node can form a cluster all by itself.

You should change the default to something appropriate to you, like your own name, to stop your nodes from trying to join another cluster on the same network with the same name!

You can do this by editing the elasticsearch.yml file in the config/ directory and then restarting Elasticsearch. When Elasticsearch is running in the foreground, you can stop it by pressing Ctrl-C; otherwise, you can shut it down with the shutdown API:

curl -XPOST 'http://localhost:9200/_shutdown'

Viewing Marvel and Sense

If you installed the Marvel management and monitoring tool, you can view it in a web browser by visiting http://localhost:9200/_plugin/marvel/.

You can reach the Sense developer console either by clicking the “Marvel dashboards” drop-down in Marvel, or by visiting http://localhost:9200/_plugin/marvel/sense/.