[
https://issues.apache.org/jira/browse/HBASE-23082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-23082:
-------------------------------
Description:
Some rebase'ing at $dayjob found that HBASE-18133 and HBASE-18135 never made it
to any branch-2's.
There's no good reason that I can think of as to why we shouldn't backport
these (will make quotas and snapshots much more accurate). As memory serves me,
they just were landing when we were branching for early 2.0.0 releases.
Let's get backports for HBASE-18133, HBASE-18135, and HBASE-20531 (and
implicitly HBASE-20439 and HBASE-20440)
was:
Some rebase'ing at $dayjob found that HBASE-18133 and HBASE-18135 never made it
to any branch-2's.
There's no good reason that I can think of as to why we shouldn't backport
these (will make quotas and snapshots much more accurate). As memory serves me,
they just were landing when we were branching for early 2.0.0 releases.
Let's get backports for HBASE-18133, HBASE-18135, and HBASE-20531.
> Backport low-latency snapshot tracking for space quotas to 2.x
> --------------------------------------------------------------
>
> Key: HBASE-23082
> URL: https://issues.apache.org/jira/browse/HBASE-23082
> Project: HBase
> Issue Type: Improvement
> Components: Quotas
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Fix For: 2.3.0, 2.1.7, 2.2.2
>
> Attachments: HBASE-23082.001.patch
>
>
> Some rebase'ing at $dayjob found that HBASE-18133 and HBASE-18135 never made
> it to any branch-2's.
> There's no good reason that I can think of as to why we shouldn't backport
> these (will make quotas and snapshots much more accurate). As memory serves
> me, they just were landing when we were branching for early 2.0.0 releases.
> Let's get backports for HBASE-18133, HBASE-18135, and HBASE-20531 (and
> implicitly HBASE-20439 and HBASE-20440)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
