[ 
https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick Branson updated CASSANDRA-7704:
------------------------------------

    Attachment: other-errors.txt

There wasn't anything in the logs that indicated *why* the failure happened. Th 
I attached anything suspect. The IndexOutOfBoundsException occurred on the 
bootstrapping node *after* the stream failure occurred on the node that was 
streaming out.

There was a CompactionTask that ran at 2014-08-05 18:00:25,804 (4 minutes 
before the StreamOut task) that tried to compact that SSTable that referenced 
in the FileNotFoundException. No other log messages related to that file though.

> FileNotFoundException during STREAM-OUT triggers 100% CPU usage
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-7704
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7704
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Rick Branson
>            Assignee: Benedict
>         Attachments: 7704.txt, backtrace.txt, other-errors.txt
>
>
> See attached backtrace which was what triggered this. This stream failed and 
> then ~12 seconds later it emitted that exception. At that point, all CPUs 
> went to 100%. A thread dump shows all the ReadStage threads stuck inside 
> IntervalTree.searchInternal inside of CFS.markReferenced().



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to