[
https://issues.apache.org/jira/browse/CASSANDRA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592489#comment-13592489
]
Yuki Morishita commented on CASSANDRA-5279:
-------------------------------------------
So, thinking this over again, I got the feeling that this is not the right way
to do.
First, right now there is no way to tell that the stream session is initiated
by which operation.
We need major redesign and that's what we should do in next streaming 2.0
(CASSANDRA-5286).
Second, we should control(start/stop/resume?) at operation level, not at stream
session level. Usually operations consist of several streams and killing one of
them causes entire operation to fail anyway.
So I'm leaning toward won't fixing this.
> 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
