You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 18:53:00 UTC

[jira] [Resolved] (HBASE-12950) Extend the truncate command to handle region ranges and not just the whole table

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

Andrew Kyle Purtell resolved HBASE-12950.
-----------------------------------------
      Assignee:     (was: Esteban Gutierrez)
    Resolution: Not A Problem

> Extend the truncate command to handle region ranges and not just the whole table
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-12950
>                 URL: https://issues.apache.org/jira/browse/HBASE-12950
>             Project: HBase
>          Issue Type: New Feature
>          Components: Region Assignment, regionserver, shell
>    Affects Versions: 2.0.0
>            Reporter: Esteban Gutierrez
>            Priority: Major
>
> We have seen many times during the last few years that when key prefixes are time based and the access pattern only consists of writes to recent KVs we can end up with tens of thousands of regions and some of those regions will not be longer used. Even if users use TTLs and data is eventually deleted we still have the old regions around and only performing an online merge can help to reduce the excess of regions. Extending the truncate command to handle also region ranges can help user that experience this issue to trim the old regions if required.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)