t; > What "design pattern" for timing did Linux violate? In other words, what
> > lesson should we be learning to assure that we don't have a similar
> problem
> > at an application level on a future leap second?
> >
> > -- Jack Krupansky
> >
> &g
o 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
>> &g
essage-
From: Óscar Marín Miró
Sent: Sunday, July 01, 2012 11:02 AM
To: solr-user@lucene.apache.org
Subject: Re: leap second bug
Thanks Michael, nice information :)
On Sun, Jul 1, 2012 at 5:29 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
Looks like this is a low-leve
Tsadikov >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.
> >>
> >>
> >>
)
>
> On Sun, Jul 1, 2012 at 1:22 PM, Michael Tsadikov
> 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.
>>
>>
>
ell, 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
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/
