[
https://issues.apache.org/jira/browse/CASSANDRA-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173441#comment-15173441
]
Marco Cadetg commented on CASSANDRA-11172:
------------------------------------------
I had to bring the cluster into a healthy state and deleted the whole keyspace
which was affected. Node that to me it seemed that the problem somehow spread
from first only occurring on one node and then spread to other nodes. Also I
guess rate limiting the amount of how many times this log message gets logged
would be nice in order to be able to debug issues.
Since the deletion of the whole keyspace I haven't seen any issues.
> Infinite loop bug adding high-level SSTableReader in compaction
> ---------------------------------------------------------------
>
> Key: CASSANDRA-11172
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11172
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: DSE 4.x / Cassandra 2.1.11.969
> Reporter: Jeff Ferland
> Assignee: Marcus Eriksson
> Fix For: 2.1.14, 2.2.6, 3.0.4, 3.4
>
> Attachments: beep.txt, tpstats.txt, tpstats_compaction.txt,
> trapped_in_compaction.txt, trapped_in_compaction_mixed.txt
>
>
> Observed that after a large repair on LCS that sometimes the system will
> enter an infinite loop with vast amounts of logs lines recording, "Adding
> high-level (L${LEVEL}) SSTableReader(path='${TABLE}') to candidates"
> This results in an outage of the node and eventual crashing. The log spam
> quickly rotates out possibly useful earlier debugging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
