[
https://issues.apache.org/jira/browse/CASSANDRA-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-5255:
-----------------------------
Attachment: 0001-Cassandra-5255.patch
Attached patch fixes the negative severity.
{quote}
we should report based on how much IO we're using, since a 1T throttled to
5MB/s is less impactful than a 100MB running at full speed
{quote}
Well I am not sure about that, 100MB without throttle may be on SSD's and 1TB
may be on Spindles.... So looking at the throttle might not help and we should
assume the user did the right thing on throttle.
Another possible option: Create a way to get IOStat data into the JVM and
measure the IOWait time but the problem is how do we support MS Windows? not
sure if there is a generic way to do so.
I would suggest we do both Streaming and IOWait monitor in another ticket,
Makes sense?
> dsnitch severity is not correctly set for compaction info
> ---------------------------------------------------------
>
> Key: CASSANDRA-5255
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5255
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.2.2
>
> Attachments: 0001-Cassandra-5255.patch
>
>
> We're doing two things wrong in CI. First, load can change between calls,
> which can cause a negative severity even though it meant to subtract whatever
> it added before. Second, we should report based on how much IO we're using,
> since a 1T throttled to 5MB/s is less impactful than a 100MB running at full
> speed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
