Dylan Pierce
Aug 25, 2017 · 1 min read

I too feel like a lone ship in these Elasticsearch testing waters.

If you like me are having trouble starting a TestCluster, it’s probably because you haven’t set the command to your elasticsearch executable. I thought installing via Homebrew would do the trick and add elasticsearch to your $PATH but apparently Elasticsearch’s TestCluster is very brittle.

You need to define your executable’s path to the command param or use the environment variable : TEST_CLUSTER_COMMAND: ‘./tmp/elasticsearch-5.2.2/bin/elasticsearch’

The de facto documentation for these things are in the Repo. But the issues conversations are especially helpful:
https://github.com/elastic/elasticsearch-ruby/issues/418

)

    Dylan Pierce

    Written by

    Software Engineer || Tiny House Builder || Smart Mirror Innovator