You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/10/17 22:50:00 UTC

[jira] [Updated] (HBASE-30483) Namespace region quota count is not updated correctly after truncating a table

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

ASF GitHub Bot updated HBASE-30483:
-----------------------------------
    Labels: pull-request-available  (was: )

> Namespace region quota count is not updated correctly after truncating a table
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-30483
>                 URL: https://issues.apache.org/jira/browse/HBASE-30483
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Yurong Fu
>            Priority: Major
>              Labels: pull-request-available
>
> When a table is truncated without preserving its splits, the old regions are replaced by a new primary region. However, the namespace region quota count maintained in NamespaceStateManager may still reflect the number of regions before truncation. 
> For example, suppose a namespace has a region quota of 2 and a table has 2 primary regions. After truncating the table without preserving splits, the table has only 1 primary region, but the cached namespace region count may remain at 2. A subsequent split can then be rejected with a QuotaExceededException, even though the split would only bring the actual region from 1 to 2.
> Expected Behavior:
> After truncation, the namespace region quota count should reflect the number of primary regions in the replacement table. 
> Actual Behavior:
> The cached region count may remain stale after truncation, causing valid region operations to be rejected.



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