Closed joshuacross closed 6 years ago
So it turns out the reason for this was that within elasticsearch.yaml action.auto_create_index
was set to false and therefore was preventing ElasticHQ from creating a .elastichq index. By default it is set to true.
Interesting. This must've changed since ES 2.x. I'll add a safe catch for this 404.
General information
Issue Description
When running
python3 application.py
with a freshly cloned repo the application starts as intended. However, when attempting to run the command again after stopping it I am greeted with the output below.I'm unsure why
PUT http://localhost:9200/.elastichq/data/hqsettings?refresh=true
would be returning a 404.Source Code / Logs