You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/08/02 19:58:02 UTC

[jira] [Resolved] (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:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-4484.
---------------------------------------

    Resolution: Fixed
      Reviewer: jbellis
      Assignee: Christopher Porter  (was: Jonathan Ellis)

patch lgtm, committed.  thanks!
                
> 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.0
>            Reporter: Christopher Porter
>            Assignee: Christopher Porter
>            Priority: Minor
>             Fix For: 1.1.4
>
>
> 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