cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12876) Negative mean write latency
Date Sun, 12 Feb 2017 07:33:41 GMT

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

Jeff Jirsa updated CASSANDRA-12876:
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.11.x)
                       (was: 4.x)
                       (was: 3.0.x)
                       (was: 2.2.x)
                   4.0
                   3.11.0
                   3.0.11
                   2.2.9
    Reproduced In: 3.0.9, 2.2.8  (was: 2.2.8, 3.0.9)
           Status: Resolved  (was: Ready to Commit)

Thanks to all three of you for your help on this [~eperott] [~cnlwsu] [~alprema] ! Committed
to 2.2 as {{7e05f393f39c90ec0447b1cc893ff46901ae3071}} and merged up to 3.0, 3.11, and trunk.


> Negative mean write latency
> ---------------------------
>
>                 Key: CASSANDRA-12876
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12876
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability
>            Reporter: Kévin LOVATO
>            Assignee: Per Otterström
>             Fix For: 2.2.9, 3.0.11, 3.11.0, 4.0
>
>         Attachments: 12876-2.2.txt, 12876-2.2-v2.txt, negative_mean_details.PNG, negative_mean_periodicity.PNG,
negative_mean.png, negative_mean_read_latency.png
>
>
> The mean write latency returned by JMX turns negative every 30 minutes. As the attached
screenshots show, the value turns negative every 30 minutes after the startup of the node.
> We did not experience this behavior in 2.1.16.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message