[jira] [Comment Edited] (CASSANDRA-11172) Infinite loop bug adding high-level SSTableReader in compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208474#comment-15208474 ] Marcus Eriksson edited comment on CASSANDRA-11172 at 3/23/16 2:33 PM: -- [~marco.zattoo] I think your problem will be fixed with CASSANDRA-11373 - the exception you see will abort the compaction and cause the issues mentioned there was (Author: krummas): [~marco.zattoo] I think your problem will be fixed with CASSANDRA-11373 > 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)
[jira] [Comment Edited] (CASSANDRA-11172) Infinite loop bug adding high-level SSTableReader in compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149814#comment-15149814 ] Will Hayworth edited comment on CASSANDRA-11172 at 2/17/16 4:16 AM: Seeing this on C* 3.3 after running a full repair on another node. {{nodetool repair --full -pr -j 4 my_keyspace_name}} I can provide whatever further details you'd like, obviously. was (Author: _wsh): Seeing this on C* 3.3 after running a full repair on another node. {{nodetool repair --full -pr -j 4 my_keyspace_name}} > 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 > Attachments: beep.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)
[jira] [Comment Edited] (CASSANDRA-11172) Infinite loop bug adding high-level SSTableReader in compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148994#comment-15148994 ] Jeff Ferland edited comment on CASSANDRA-11172 at 2/16/16 6:01 PM: --- Possible duplicate of CASSANDRA-10831 ? was (Author: autocracy): Possible duplicate of https://issues.apache.org/jira/browse/CASSANDRA-10831 ? > 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 > > 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)