[
https://issues.apache.org/jira/browse/CASSANDRA-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791268#comment-14791268
]
Jeremy Hanna commented on CASSANDRA-8708:
-----------------------------------------
This is a bug that has persisted since the inter dc stream throughput throttle
was introduced in 2.0. I thought it was too late for 2.0 but since it's really
what it was supposed to be in the first place, I felt like 2.1 was fine.
Besides that I don't think anyone relies on or wants unthrottled inter dc
streaming throughput. It was discovered when when we double checked because we
thought it was 200 by default.
> 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: Core
> Reporter: Adam Hattrell
> Assignee: Jeremy Hanna
> Fix For: 2.1.x, 2.2.x
>
> Attachments: 8708-2.1-jmx-nodetool-bulkloader.txt,
> 8708-2.1-with-jmx-nodetool.txt, 8708-2.1.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)
