We're updating the issue view to help you get more done. 

Runaway ElasticSearch Log

Description

I'm an admitted n00b with ElasticSearch/Logstash. That being said I've created a simple installation of LogStash, using ElasticSearch, only monitoring syslog messages, for a POC my team is working on. This morning I came in and I had 20GB of java warnings in the ElasticSearch logs in only two days time. I'm pretty sure I've done something wrong, but everything seems to be functioning normally. I've attached an example of the warnings.

I get the same warning multiple times a second. All I'm doing to install ElasticSearch is exploding the tar ball, changing to the ElasticSearch dir, and running `bin/elasticsearch`.

I'm sure I have not provided all the info you need to assist, but any help you can provide would be greatly appreciated!!

Version of Logstash - 1.2.1
Version of ElasticSearch - elasticsearch-0.90.5
Version of your Java - java-1.7.0-openjdk-1.7.0.25-2.3.10.4.el6_4.x86_64
Operating system - RHEL 6.4

[root@rob-test logs]# curl -XGET 'http://127.0.0.1:9200/_cluster/health?pretty=true'
{
"cluster_name" : "elasticsearch",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 3,
"number_of_data_nodes" : 2,
"active_primary_shards" : 37,
"active_shards" : 50,
"relocating_shards" : 0,
"initializing_shards" : 2,
"unassigned_shards" : 28
}

Environment

None

Status

Assignee

Jason Kendall

Reporter

Rob Cantrell

Labels

Affects versions

1.2.2
1.2.1

Priority