[jira] [Updated] (CASSANDRA-16707) JmxHistogram#getRecentValues() is not thread-safe

["Caleb Rackliffe (Jira)" <ji...@apache.org>]

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

Caleb Rackliffe updated CASSANDRA-16707:
----------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Transient Incorrect Response(12987)
       Complexity: Low Hanging Fruit
    Discovered By: Code Inspection
    Fix Version/s: 4.x
                   4.0.x
         Severity: Low
           Status: Open  (was: Triage Needed)

> JmxHistogram#getRecentValues() is not thread-safe
> -------------------------------------------------
>
>                 Key: CASSANDRA-16707
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16707
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability/JMX
>            Reporter: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 4.0.x, 4.x
>
>
> Published {{JmxHistogram}} instances do not protect their “last” field. This isn’t a hot path, and there is a multi-part calculation based on it in {{getRecentValues()}}, so we should probably just synchronize that method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org