You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Christopher Porter (JIRA)" <ji...@apache.org> on 2012/08/02 18:44:02 UTC

[jira] [Commented] (CASSANDRA-4484) Drain causes incorrect error messages: "Stream took more than 24H to complete; skipping"

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

Christopher Porter commented on CASSANDRA-4484:
-----------------------------------------------

Fixed with this pull request: https://github.com/apache/cassandra/pull/12
                
> Drain causes incorrect error messages: "Stream took more than 24H to complete; skipping"
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4484
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4484
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Christopher Porter
>            Priority: Minor
>
> After calling drain on a node, there are a bunch of incorrect error messages in the cassandra log file: "Stream took more than 24H to complete; skipping".
> The problem is in MessagingService.waitForStreaming. It is logging an error if ThreadPoolExecutor.awaitTermination returns true, but if a timeout happens it returns false. See http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html#awaitTermination%28long,%20java.util.concurrent.TimeUnit%29

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira