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

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2013/08/12 20:08:48 UTC

[jira] [Resolved] (CASSANDRA-5279) Provide a nodetool command to close stream sessions

     [ https://issues.apache.org/jira/browse/CASSANDRA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita resolved CASSANDRA-5279.
---------------------------------------

    Resolution: Won't Fix

Won't fixing as of streaming 2.0 release and my comment above.
                
> Provide a nodetool command to close stream sessions 
> ----------------------------------------------------
>
>                 Key: CASSANDRA-5279
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5279
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core, Tools
>    Affects Versions: 1.1.9
>            Reporter: Ahmed Bashir
>            Assignee: Yuki Morishita
>
> It would be quite useful to be able to close stream sessions (derived from AbstractStreamSession) via nodetool.
> This could be done in total or by session ID (all stream sessions have an ID).
> Stream sessions can be long-running, cause load on the network, send a very large amount of data to endpoints, and trigger large amount of pending compaction tasks.  Just like we make it possible to cancel compaction, it is very useful to be able to close these sessions via nodetool (close() is if such sessions are affecting cluster stability (which they can)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira