Benedict commented on CASSANDRA-7704:

[~rbranson], ftr, could we get the earlier stack traces you saw and other 
related info? I suspect it's possible the earlier failing transfer caused a 
file to be deleted prematurely, which then caused this failure. Both the same 

> 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
> 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

Reply via email to