[
https://issues.apache.org/jira/browse/CASSANDRA-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168934#comment-15168934
]
Marco Cadetg commented on CASSANDRA-11172:
------------------------------------------
[~krummas] I've restarted nodes many times and the issue just comes up again.
Does this mean that it is not related to the fix you've done? The issue happens
during normal compactions on just restarted node after some time (I think after
it tries to do the first compaction) with the result that the system.log starts
get spammed with the infinite amount to the messages.
{code}
INFO [CompactionExecutor:5] 2016-02-26 05:45:56,479 LeveledManifest.java:438 -
Adding high-level (L3)
BigTableReader(path='/var/lib/cassandra/data2/ham/raw_sessions-417de7c0bb4711e4972d05e7bd5b0c2f/ma-45159-big-Data.db')
to candidates
{code}
> 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_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)
