[ 
https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099527#comment-14099527
 ] 

Benedict commented on CASSANDRA-7704:
-------------------------------------

Committed to 2.0, 2.1.0 and 2.1 branches. I overwrote 2.0's contents with 
2.1's, only removing the repairedAt property, since the only other difference 
was the lack of aborted property preventing inconsistent state.

> 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
>             Fix For: 2.0.10, 2.1.0
>
>         Attachments: 7704-2.1.txt, 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