[jira] [Resolved] (HBASE-28349) Atomic requests should increment read usage in quotas

["Bryan Beaudreault (Jira)" <ji...@apache.org>]

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

Bryan Beaudreault resolved HBASE-28349.
---------------------------------------
    Fix Version/s: 2.6.0
                   3.0.0-beta-2
     Release Note: Conditional atomic mutations which involve a read-modify-write (increment/append) or check-and-mutate, will now count as both a read and write when evaluating quotas. Previously they would just count as a write, despite involving a read as well.
       Resolution: Fixed

> Atomic requests should increment read usage in quotas
> -----------------------------------------------------
>
>                 Key: HBASE-28349
>                 URL: https://issues.apache.org/jira/browse/HBASE-28349
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ray Mattingly
>            Assignee: Ray Mattingly
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.6.0, 3.0.0-beta-2
>
>
> Right now atomic operations are just treated as a single write from the quota perspective. Since an atomic operation also encompasses a read, it would make sense to increment readNum and readSize counts appropriately.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)