Yes, but why is the cluster red? Did you issue the _cat/indices RPC immediately after the index was created? After creating an index the cluster should go yellow within a second or two.
Yes, because Logstash by default attempts to join a cluster named "elasticsearch" (see the documentation of the cluster parameter) and when you rename the cluster Logstash won't find any cluster with that name to connect to. Make sure ES and LS agree on the cluster name, or make Logstash use HTTP instead with protocol => http.
Yes, but why is the cluster red? Did you issue the _cat/indices RPC immediately after the index was created? After creating an index the cluster should go yellow within a second or two.
Yep. You're right. It was red because I curled the indexes a little too quickly. I started from scratch with the default yaml file, plus I added one more node.
green open .kibana 1 1 2 0 9.5kb 4.8kb
green open logstash-2015.06.24 5 1 7 0 38.2kb 19.2kb
So, I'm all good there now.
Yes, because Logstash by default attempts to join a cluster named "elasticsearch" (see the documentation of the cluster parameter) and when you rename the cluster Logstash won't find any cluster with that name to connect to. Make sure ES and LS agree on the cluster name, or make Logstash use HTTP instead with protocol => http.
Ok that makes sense. Is there an easy way to get LS to look for a different cluster name? One of my choosing? Or maybe just using http mode would be easier.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.