[
https://issues.apache.org/jira/browse/CASSANDRA-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095009#comment-13095009
]
Stu Hood edited comment on CASSANDRA-3080 at 9/1/11 12:07 AM:
--------------------------------------------------------------
Attaching an example TRACE log from a stream throttling session (grep
'Stream'). The throttling is fairly bursty because we send 10 MB chunks, but
since these are sub-100ms bursts, I'm not sure its worth worrying about.
was (Author: stuhood):
Attaching an example log from a stream throttling session (grep 'Stream').
The throttling is fairly bursty because we send 10 MB chunks, but since these
are sub-second 100ms bursts, I'm not sure its worth worrying about.
> Add throttling for internode streaming
> --------------------------------------
>
> Key: CASSANDRA-3080
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3080
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Assignee: Stu Hood
> Fix For: 1.0
>
> Attachments: 0001-Extract-throttling-into-a-Throttle-class.txt,
> 0002-Remove-orphaned-throttling-path.txt,
> 0003-Add-stream_throughput_outbound_megabits_per_sec-settin.txt,
> 0004-Add-outbound-stream-throttling.txt, stream-throttling-example.log
>
>
> Cassandra does (mostly) sequential reads from disk to send data to other
> nodes, which means that it is easily possible to stream upwards of 100 MB/s
> per source node.
> To avoid affecting service, we should add streaming throttling across all
> streams in the outbound direction, preferably configurable from JMX, and with
> `nodetool netstats` integration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
