[
https://issues.apache.org/jira/browse/HBASE-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-23222.
---------------------------------
Fix Version/s: 2.2.3
2.1.8
2.3.0
3.0.0
Release Note:
<!-- markdown -->
The MOB compaction process in the HBase Master now logs more about its activity.
In the event that you run into the problems described in HBASE-22075, there is
a new HFileCleanerDelegate that will stop all removal of MOB hfiles from the
archive area. It can be configured by adding
`org.apache.hadoop.hbase.mob.ManualMobMaintHFileCleaner` to the list configured
for `hbase.master.hfilecleaner.plugins`. This new cleaner delegate will cause
your archive area to grow unbounded; you will have to manually prune files
which may be prohibitively complex. Consider if your use case will allow you to
mitigate by disabling mob compactions instead.
Caveats:
* Be sure the list of cleaner delegates still includes the default cleaners you
will likely need: ttl, snapshot, and hlink.
* Be mindful that if you enable this cleaner delegate then there will be *no*
automated process for removing these mob hfiles. You should see a single region
per table in `%hbase_root%/archive` that accumulates files over time. You will
have to determine which of these files are safe or not to remove.
* You should list this cleaner delegate after the snapshot and hlink delegates
so that you can enable sufficient logging to determine when an archived mob
hfile is needed by those subsystems. When set to `TRACE` logging, the
CleanerChore logger will include archive retention decision justifications.
* If your use case creates a large number of uniquely named tables, this new
delegate will cause memory pressure on the master.
Resolution: Fixed
> Better logging and mitigation for MOB compaction failures
> ---------------------------------------------------------
>
> Key: HBASE-23222
> URL: https://issues.apache.org/jira/browse/HBASE-23222
> Project: HBase
> Issue Type: Bug
> Components: mob
> Affects Versions: 2.1.0, 2.0.0, 2.2.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
>
> Some logging and mitigation options for MOB dataloss issues described in
> HBASE-22075.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
