[
https://issues.apache.org/jira/browse/CASSANDRA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584734#comment-13584734
]
Ahmed Bashir commented on CASSANDRA-5279:
-----------------------------------------
Sessions can be distinguished by their session ID, right?
> 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
