[
https://issues.apache.org/jira/browse/CASSANDRA-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076194#comment-15076194
]
Jeremy Hanna commented on CASSANDRA-8708:
-----------------------------------------
||Code||DTests||
|[2.1
branch|https://github.com/jeromatron/cassandra/tree/8708-2.1]|[dtest|http://cassci.datastax.com/job/jeromatron-8708-2.1-dtest/]|
|[2.2
branch|https://github.com/jeromatron/cassandra/tree/8708-2.2]|[dtest|http://cassci.datastax.com/job/jeromatron-8708-2.2-dtest/]|
|[3.0
branch|https://github.com/jeromatron/cassandra/tree/8708-3.0]|[dtest|http://cassci.datastax.com/job/jeromatron-8708-3.0-dtest/]|
|[trunk|https://github.com/jeromatron/cassandra/tree/8708-trunk]|[dtest|http://cassci.datastax.com/job/jeromatron-8708-trunk-dtest/]|
> inter_dc_stream_throughput_outbound_megabits_per_sec to defaults to unlimited
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-8708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8708
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Adam Hattrell
> Assignee: Jeremy Hanna
> Labels: docs-impacting
> Fix For: 2.1.x, 2.2.x
>
> Attachments: 8708-2.1-jmx-nodetool-bulkloader-v2.txt,
> 8708-2.1-jmx-nodetool-bulkloader-v3.txt,
> 8708-2.1-jmx-nodetool-bulkloader.txt, 8708-2.1-with-jmx-nodetool.txt,
> 8708-2.1.txt, 8708-2.2.txt
>
>
> inter_dc_stream_throughput_outbound_megabits_per_sec was introduced in
> CASSANDRA-6596.
> There's some discussion in the ticket of the intention to link the default to
> whatever stream_throughput_outbound_megabits_per_sec is set to.
> However, it looks like it's just set to 0 - from
> /src/java/org/apache/cassandra/config/Config.java
> This is a bit of a pain - usually folks want to set the inter dc limits lower
> than the base streaming figure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
