[
https://issues.apache.org/jira/browse/CASSANDRA-7330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053093#comment-14053093
]
Dmitry Mitko commented on CASSANDRA-7330:
-----------------------------------------
Gents, I had a bad situation in some cassandra (2.0.7) nodes, when they were
eaten all CPU during streaming (during joining node or repairing procedure).
The result is - a huge cpu loading of nodes, slow responses, mistakes in
OpsCenter, slow service...
I didn't find anything useful in logs, any weird WARNs or ERRORs. Cassandra
behavour is similar to infinite loop, node manual restarting solves the
situation. That's why I decided to write here.
Can be my situation is the same with yours or it is a different sitatuon?
P.S.: I'll monitor similar problems with Cassandra 2.0.9, of course.
> Infinite loop in StreamReader.read during exception condition while running
> repair
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-7330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7330
> Project: Cassandra
> Issue Type: Bug
> Environment: 2.0.8+
> Reporter: Joshua McKenzie
> Assignee: Joshua McKenzie
> Priority: Minor
> Labels: Core
> Fix For: 2.0.9
>
> Attachments: 7330_v1.txt
>
>
> InputStream.skip is returning -1 during exception conditions which leads the
> following logic to infinite loop:
> {code:title=loop}
> protected void drain(InputStream dis, long bytesRead) throws IOException
> {
> long toSkip = totalSize() - bytesRead;
> toSkip = toSkip - dis.skip(toSkip);
> while (toSkip > 0)
> toSkip = toSkip - dis.skip(toSkip);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
