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:42:04 UTC
[jira] [Created] (CASSANDRA-4484) Drain causes incorrect error
messages: "Stream took more than 24H to complete; skipping"
Christopher Porter created CASSANDRA-4484:
---------------------------------------------
Summary: 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
[jira] [Commented] (CASSANDRA-4484) Drain causes incorrect error
messages: "Stream took more than 24H to complete; skipping"
Posted by "Christopher Porter (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-4484) Drain causes incorrect error
messages: "Stream took more than 24H to complete; skipping"
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4484:
--------------------------------------
Affects Version/s: (was: 1.1.1)
1.1.0
Fix Version/s: 1.1.4
Assignee: Jonathan Ellis
(Introduced in CASSANDRA-3679 for 1.1.0.)
> 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: Jonathan Ellis
> 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
[jira] [Resolved] (CASSANDRA-4484) Drain causes incorrect error
messages: "Stream took more than 24H to complete; skipping"
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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