[
https://issues.apache.org/jira/browse/CASSANDRA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044580#comment-14044580
]
Robert Stupp edited comment on CASSANDRA-6596 at 6/26/14 11:28 AM:
-------------------------------------------------------------------
--As far as I can see this fix (SHA
[ea28d36892b72480495629d8df3468f8ecfc9764|https://github.com/apache/cassandra/commit/ea28d36892b72480495629d8df3468f8ecfc9764])
has been committed on 2.0 branch on Feb 16th and merged into trunk. 2.1 branch
was created one day after ;)--
Sorry - I'm wrong :(
was (Author: snazy):
As far as I can see this fix (SHA
[ea28d36892b72480495629d8df3468f8ecfc9764|https://github.com/apache/cassandra/commit/ea28d36892b72480495629d8df3468f8ecfc9764])
has been committed on 2.0 branch on Feb 16th and merged into trunk. 2.1 branch
was created one day after ;)
> Split out outgoing stream throughput within a DC and inter-DC
> -------------------------------------------------------------
>
> Key: CASSANDRA-6596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6596
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeremy Hanna
> Assignee: Vijay
> Priority: Minor
> Fix For: 2.1 beta1
>
> Attachments: 0001-CASSANDRA-6596.patch
>
>
> Currently the outgoing stream throughput setting doesn't differentiate
> between when it goes to another node in the same DC and when it goes to
> another DC across a potentially bandwidth limited link. It would be nice to
> have that split out so that it could be tuned for each type of link.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
