cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Jirsa <jji...@gmail.com>
Subject Re: Restarting an existing node hangs
Date Wed, 23 Aug 2017 18:19:24 GMT
jstack to dump threads, get a heap dump, or turn up your logging (to debug
or trace) until you can figure out what exactly it's doing.



On Wed, Aug 23, 2017 at 11:16 AM, Mark Furlong <mfurlong@ancestry.com>
wrote:

> Cassandra doesn’t exit and continues to run with very little CPU usage
> shown in top.
>
>
>
> *Thanks*
>
> *Mark*
>
> *801-705-7115 <(801)%20705-7115> office*
>
>
>
> *From:* Jeff Jirsa [mailto:jjirsa@gmail.com]
> *Sent:* Wednesday, August 23, 2017 12:07 PM
> *To:* cassandra <user@cassandra.apache.org>
> *Subject:* Re: Restarting an existing node hangs
>
>
>
> Typically if that sstable is damaged you'd see some sort of message. If
> you recently changed bloom filter or index intervals for that table, it may
> be silently rebuilding the other components of that sstable. Does cassandra
> exit or does it just keep churning away?
>
>
>
>
>
>
>
> On Wed, Aug 23, 2017 at 10:20 AM, Mark Furlong <mfurlong@ancestry.com>
> wrote:
>
> I had an existing node go down. I don’t know the cause of this. I am
> starting Cassandra and I can see in the log that it starts and then hangs
> on the opening of an sstable. Is there anything I can do to fix the sstable?
>
>
>
> I’m on OSC 2.1.12.
>
>
>
> *Thanks in advance,*
>
> *Mark Furlong*
>
> Sr. Database Administrator
>
> *mfurlong@ancestry.com <mfurlong@ancestry.com>*
> M: 801-859-7427 <(801)%20859-7427>
>
> O: 801-705-7115 <(801)%20705-7115>
>
> 1300 W Traverse Pkwy
>
> Lehi, UT 84043
>
>
>
>
>
> ​[image: http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]
>
>
>
>
>
>
>

Mime
View raw message