Hi Jörg, Sure, my bad. There is no OOM and here is the second gist, https://gist.github.com/jasonwee/8294514 . The exceptions are repetitive, so that explains large number of lines in the log file.
Does the second gist help to determine the problem? I can get the log if it does not tell where might be the cause. Thank you again for helps. Jason On Tue, Jan 7, 2014 at 3:30 AM, joergpra...@gmail.com <joergpra...@gmail.com > wrote: > I was not speaking of the whole logfile, but the whole stacktrace, just to > make sure where the culprit started. If there was no OOM or other things > around, it would be surprising. > > Jörg > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFi-T8iiKTULr_S-7OddJnAoGGF4%3Db6reB3vGejDArgnQ%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itw2EJvBU2wt1KeXg4xjuPVK6B-7UK8kJMtj56R1E3owcg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
