Looks like this is a low-level Linux issue ... see Shay's email to the
ElasticSearch list about it:
https://groups.google.com/forum/?fromgroups#!topic/elasticsearch/_I1_OfaL7QY
Also see the comments here:
http://news.ycombinator.com/item?id=4182642
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 1, 2012 at 8:08 AM, Óscar Marín Miró
<oscarmarinm...@gmail.com> wrote:
> Hello Michael, thanks for the note :)
>
> I'm having a similar problem since yesterday, tomcats are wild on CPU [near
> 100%]. Did your solr servers did not reply to index/query requests?
>
> Thanks :)
>
> On Sun, Jul 1, 2012 at 1:22 PM, Michael Tsadikov
> <mich...@myheritage.com>wrote:
>
>> Our solr servers went into GC hell, and became non-responsive on date
>> change today.
>>
>> Restarting tomcats did not help.
>>
>> Rebooting the machine did.
>>
>>
>> http://www.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/
>>
>
>
>
> --
> Whether it's science, technology, personal experience, true love,
> astrology, or gut feelings, each of us has confidence in something that we
> will never fully comprehend.
> --Roy H. William
