>
>
> *Thanks*
>
> *Mark*
>
> *801-705-7115 <(801)%20705-7115> office*
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com]
> *Sent:* Wednesday, August 23, 2017 12:07 PM
> *To:* cassandra
> *Subject:* Re: Restarting an existing node hangs
>
Cassandra doesn’t exit and continues to run with very little CPU usage shown in
top.
Thanks
Mark
801-705-7115 office
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Wednesday, August 23, 2017 12:07 PM
To: cassandra
Subject: Re: Restarting an existing node hangs
Typically if that sstable is
See also: https://issues.apache.org/jira/browse/CASSANDRA-11163
On Wed, Aug 23, 2017 at 11:07 AM, Jeff Jirsa wrote:
> 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
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 A
