[hbase] branch master updated: HBASE-25669 Fix typo of hbase.mob.compaction.chore.period in the docs (#3056)

[st...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

stack pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/master by this push:
     new 75931b4  HBASE-25669 Fix typo of hbase.mob.compaction.chore.period in the docs (#3056)
75931b4 is described below

commit 75931b45905d98651d06cc01a554c119ddbddc0e
Author: Norbert Kalmar <nk...@cloudera.com>
AuthorDate: Wed Mar 17 04:58:56 2021 +0100

    HBASE-25669 Fix typo of hbase.mob.compaction.chore.period in the docs (#3056)
---
 src/main/asciidoc/_chapters/hbase_mob.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main/asciidoc/_chapters/hbase_mob.adoc b/src/main/asciidoc/_chapters/hbase_mob.adoc
index 467d35c..9b67c6e 100644
--- a/src/main/asciidoc/_chapters/hbase_mob.adoc
+++ b/src/main/asciidoc/_chapters/hbase_mob.adoc
@@ -469,7 +469,7 @@ reloaded.
 
 .Procedure: Stop MOB maintenance, change MOB threshold, rewrite data via compaction
 . Ensure the MOB compaction chore in the Master is off by setting
-`hbase.mob.file.compaction.chore.period` to `0`. Applying this configuration change will require a
+`hbase.mob.compaction.chore.period` to `0`. Applying this configuration change will require a
 rolling restart of HBase Masters. That will require at least one fail-over of the active master,
 which may cause retries for clients doing HBase administrative operations.
 . Ensure no MOB compactions are issued for the table via the HBase shell for the duration of this
@@ -598,7 +598,7 @@ Done.
 ----
 . After the column family no longer shows the MOB feature enabled, it is safe to start MOB
 maintenance chores again. You can allow the default to be used for
-`hbase.mob.file.compaction.chore.period` by removing it from your configuration files or restore
+`hbase.mob.compaction.chore.period` by removing it from your configuration files or restore
 it to whatever custom value you had prior to starting this process.
 . Once the MOB feature is disabled for the column family there will be no internal HBase process
 looking for data in the MOB storage area specific to this column family. There will still be data