elasticsearch_http fails to create a new index with automatic index creation disabled in ES


Hey guys,

We're running logstash against ES 0.90 and our ES servers have action.auto_create_index setting set to false (we have reasons for that). We've been using elasticsearch output for a while, but there are some issues with it (most probably caused by 0.20-0.90 incomptibilities) that made us look at elasticsearch_http output. This output worked better for a day and then blew up at midnight failing to create a new index and trying to write batches of log records to non-existing index and failing with a 404.

I'm not sure if it is an oversight or an intentional design decision, but either way I think it needs to at least be documented in elasticsearch_http docs.



Logstash Developers


Oleksiy Kovyrin

Affects versions