[
https://issues.apache.org/jira/browse/HBASE-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-5147.
-----------------------------------
Resolution: Not A Problem
> Compaction/Major compaction operation from shell/API/JMX
> --------------------------------------------------------
>
> Key: HBASE-5147
> URL: https://issues.apache.org/jira/browse/HBASE-5147
> Project: HBase
> Issue Type: New Feature
> Components: master, regionserver, shell
> Affects Versions: 0.90.1, 0.90.2, 0.92.0
> Reporter: Mikael Sitruk
>
> Compaction handling is important internal process nevertheless when it occurs
> it can have dramatic impact on cluster performance (especially when the
> cluster growth uniformly).
> Secondly current operations enabled are just to trigger a compaction process
> without possibility to know what is its status. Making very unconvenient to
> manage compaction manually.
> This JIRA suggests to allow management of compaction from different
> interfaces - Shell, API, JMX
> Following is the list of requested operations
> 1. getting compaction status - which server/region is under compaction and
> what is compacted (currently this info is only via log)
> 2. % of uncompacted files
> 3. Possibility to stop major compaction
> 4. Starting compaction from JMX (other interface already support this)
> Note - part of these requirements are also suggested in HBASE-3965
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
