cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9714) sstableloader appears to use the cassandra.yaml outgoing stream throttle
Date Tue, 09 Feb 2016 03:45:18 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita updated CASSANDRA-9714:
--------------------------------------
    Fix Version/s: 3.x
                   3.0.x
                   2.2.x
                   2.1.x

> sstableloader appears to use the cassandra.yaml outgoing stream throttle
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9714
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9714
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Jeremy Hanna
>            Assignee: Yuki Morishita
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> When trying to use the sstableloader, we found (through the metrics in opscenter) that
the stream throughput was constant at about 24MB/s.  We didn't run it with the --throttle
option so according to the help output and the BulkLoader code it should be unthrottled. 
However when it was unthrottled in the cassandra.yaml in the loader's classpath, it got up
to the low hundreds of MB/s.    It sounds like when starting up it takes the cassandra.yaml
attributes and overrides the default throttle setting of the loader.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message