[
https://issues.apache.org/jira/browse/CASSANDRA-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075292#comment-15075292
]
Ariel Weisberg commented on CASSANDRA-8708:
-------------------------------------------
Local results don't matter only what Cassci thinks matters because some things
will persistently pass locally but fail in Cassci. What you can do is look at
the the test history for the branch you started off of and if it is failing
there as well we don't let it block commit right now.
I checked the 2.1 branch and it seems to be about as good as the unmodified 2.1
branch. Will do the same for the others once they finish.
> 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.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)
