Yes you can rename it using
http://logstash.net/docs/1.3.1/outputs/elasticsearch#node_name
You have a real problem here as your cluster should not be red.
But it should not be caused by the logstash node.
Did you set embedded to false (it's default on 1.3.1 but not sure about
previous version)?
What gives the following?
curl -XGET 'http://localhost:9200/_cluster/state?pretty'
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 17 décembre 2013 at 20:34:43, Eric Luellen (eric.luel...@gmail.com) a écrit:
Hmmm. I'm not sure why my status is red then
I ran that command and saw some fairly old files that were no longer there
that it was trying to read. I believe Elasticsearch got behind on indexing
the files and they were removed before it could finish. I'm not sure but
that's just a guess. I have removed all of the files and started fresh.
Thanks for the information. I don't mind it being there, I would just
confused of why it was there. If it stays there, will my cluster status
continue to show red on the health? That was my main concern. Also, if it
stays there, I wish I could rename it from the default Lupo it is to the
name o
Hmmm. I'm not sure why my status is red then. The only thing I can see from
the cluster-health documentation page is that a specific shard is not
allocated in the cluster. When I look at my cluster health, I do see this:
"unassigned_shards" : 60
Guess I need to figure out why I have so many
I'd not worry of the non data node.
It's only a node which connect to the cluster to give a client to logstash.
If you really don't want it, then you can use
http://logstash.net/docs/1.3.1/outputs/elasticsearch_http
HTH
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @ela
I am working on building out a small POC for Logstash and Elasticsearch. To
start, I have a 2 server setup.
- Server 1 - logstash1 - running "java -jar logstash-1.2.2-flatjar.jar
agent -f indexer.conf"
- This server is tailing logs from a syslog config file and then sending
the
