logstash - Exception in thread "output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]

Question

Log stash is 100% a disaster for me. I am using LS 1.4.1 and ES 1.02 in the same machine. Here is how I start logstash indexer: ``` /usr/local/share/logstash-1.4.1/bin/logstash -f /usr/local/share/logstash.indexer.config input { redis { host => "redis.queue.do.development.sf.test.com" data_type => "list" key => "logstash" codec => json } } output { stdout { } elasticsearch { bind_host => "127.0.0.1" port => "9300" } } ``` ES I set: ``` network.bind_host: 127.0.0.1 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300"] ``` And wow..this is what I get: ``` /usr/local/share/logstash-1.4.1/bin/logstash -f /usr/local/share/logstash.indexer.config Using milestone 2 input plugin 'redis'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see http://logstash.net/docs/1.4.1/plugin-milestones {:level=>:warn} log4j, [2014-05-29T12:02:29.545] WARN: org.elasticsearch.discovery: [log…

Accepted Answer

See http://logstash.net/docs/1.4.1/outputs/elasticsearch

VERSION NOTE: Your Elasticsearch cluster must be running Elasticsearch 1.1.1. If you use any other version of Elasticsearch, you should set protocol => http in this plugin.

So your problem is that logstash doesn't support the older ES version you are using without using an `http` transport.

logstash - Exception in thread ">output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]

Solution

Problem