You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/07/26 10:05:00 UTC
[jira] [Updated] (HBASE-20946) HMaster UI warn if Major Compaction
hasn't occurred after hbase.hregion.majorcompaction time
[ https://issues.apache.org/jira/browse/HBASE-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Sekhon updated HBASE-20946:
--------------------------------
Summary: HMaster UI warn if Major Compaction hasn't occurred after hbase.hregion.majorcompaction time (was: HMaster UI warn if Major Compaction hasn't occurred + completed successfully within hbase.hregion.majorcompaction time)
> HMaster UI warn if Major Compaction hasn't occurred after hbase.hregion.majorcompaction time
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-20946
> URL: https://issues.apache.org/jira/browse/HBASE-20946
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0, 1.1.2, 2.2.0
> Reporter: Hari Sekhon
> Priority: Major
>
> HMaster UI should warn if Major Compaction hasn't occurred and completed successfully within hbase.hregion.majorcompaction time (default 7 days).
> Recent changes in HBase HBASE-6028 mean major compactions could be cancelled and result in read amplification over time. HMaster UI should monitor time since last major compaction completed successfully isn't greater than hbase.hregion.majorcompaction (plus some fudge factor).
> If hbase.hregion.majorcompaction is zero then disable the check, as external tooling will trigger major compactions off peak and should instead monitor against JMX timestamp of last major compaction as per HBASE-20945.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)