incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From feedly team <feedly...@gmail.com>
Subject Re: frequent node up/downs
Date Tue, 03 Jul 2012 01:51:27 GMT
Yeah I noticed the leap second problem and ran the suggested fix, but I
have been facing these problems before Saturday and still see the
occasional failures after running the fix.

Thanks.

On Mon, Jul 2, 2012 at 11:17 AM, Marcus Both <mboth@terra.com.br> wrote:

> Yeah! Look that.
>
> http://arstechnica.com/business/2012/07/one-day-later-the-leap-second-v-the-internet-scorecard/
> I had the same problem. The solution was rebooting.
>
> On Mon, 2 Jul 2012 11:08:57 -0400
> feedly team <feedlydev@gmail.com> wrote:
>
> > Hello,
> >    I recently set up a 2 node cassandra cluster on dedicated hardware. In
> > the logs there have been a lot of "InetAddress xxx is now dead' or UP
> > messages. Comparing the log messages between the 2 nodes, they seem to
> > coincide with extremely long ParNew collections. I have seem some of up
> to
> > 50 seconds. The installation is pretty vanilla, I didn't change any
> > settings and the machines don't seem particularly busy - cassandra is the
> > only thing running on the machine with an 8GB heap. The machine has 64GB
> of
> > RAM and CPU/IO usage looks pretty light. I do see a lot of 'Heap is xxx
> > full. You may need to reduce memtable and/or cache sizes' messages. Would
> > this help with the long ParNew collections? That message seems to be
> > triggered on a full collection.
>
> --
> Marcus Both
>
>

Mime
View raw message