[
https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096146#comment-14096146
]
Yuki Morishita commented on CASSANDRA-7704:
-------------------------------------------
{{complete}} calls {{cancel}} with interuption on ScheduledFuture, but since
{{complete}} is also called from scheduled task, ScheduledFuture#get always
throws CancellationException even if it is run. This is causing
StreamTransferTaskTest to fail.
Though returned ScheduledFuture is not used in production code, I feel the new
behavior confusing.
I wrote the original to just let scheduled task run even if task is completed
and noop. Can we do it in similar way?
> 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.20.v2.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)
