ElasticSearch Crash -- Can't seem to find anything in the log files

I've had ElasticSearch crash twice on my production servers in the last 24 hours. This has me very concerned; I can't afford to have this kind of instability. I'd really appreciate any insight anyone can provide.

[[EDIT]] 4 crashes now in 3 days.

I'm running v0.20.5 on EC2 with 2 nodes in my cluster. I'm running with 4GB of RAM allocated to ES and 64k max open files. I'm not seeing anything interesting in the log files, at least to my eyes. There are a fair number of "failed to execute search request" errors, but this is because I've exposed the search portion of my API, and others are bound to accidentally mis-use the search queries (I have not exposed anything but searching a single index). Other than that, I don't see anything else in the logs.

Here's the full log file: http://streamified.com/downloads/streamified.txt

What do you mean by crash? Does elasticsearch process just disappear? Which
version of java are you using?

On Saturday, March 23, 2013 9:18:37 PM UTC-4, Zane Claes wrote:

I've had ElasticSearch crash twice on my production servers in the last 24
hours. This has me very concerned; I can't afford to have this kind of
instability. I'd really appreciate any insight anyone can provide.

I'm running v0.20.5 on EC2 with 2 nodes in my cluster. I'm running with
4GB
of RAM allocated to ES and 64k max open files. I'm not seeing anything
interesting in the log files, at least to my eyes. There are a fair number
of "failed to execute search request" errors, but this is because I've
exposed the search portion of my API, and others are bound to accidentally
mis-use the search queries (I have not exposed anything but searching a
single index). Other than that, I don't see anything else in the logs.

Here's the full log file: http://streamified.com/downloads/streamified.txt

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-Crash-Can-t-seem-to-find-anything-in-the-log-files-tp4032235.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hm, yes, the process "just disappears." I guess I assumed that meant a crash, but I don't know how to verify. Java:

java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)

When java crashes it sometimes leaves behind java_pid.hprof files
where is pid of the java process that crashed. With elasticsearch it
typically happens when elasticsearch runs on an old versions of java. So, I
would recommend upgrading to the latest version of java 7 or at least the
latest version of java 6.

On Monday, March 25, 2013 9:44:49 PM UTC-4, Zane Claes wrote:

Hm, yes, the process "just disappears." I guess I assumed that meant a
crash,
but I don't know how to verify. Java:

java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-Crash-Can-t-seem-to-find-anything-in-the-log-files-tp4032235p4032346.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

I also face the same issue with 1.7 version of Java.

Thanks,
Sumit