anchor.diff:  hbase> major_compact_mob 't1'
   ----
   
  -These commands are also available via `Admin.compactMob` and `Admin.majorCompactMob` methods.
  +These commands are also available via `Admin.compactMob` and
  +`Admin.majorCompactMob` methods.
   
   ==== MOB Sweeper
   
  -HBase MOB currently relies on a MapReduce job called the Sweeper tool for optimization. The Sweeper tool oalesces small MOB files or MOB files with many deletions or updates. A native MOB compaction tool is still in testing. To configure the Sweeper tool, set the following options:
  +HBase MOB a MapReduce job called the Sweeper tool for
  +optimization. The Sweeper tool oalesces small MOB files or MOB files with many
  +deletions or updates. The Sweeper tool is not required if you use native MOB compaction, which
  +does not rely on MapReduce.
  +
  +To configure the Sweeper tool, set the following options:
   
   [source,xml]
   ----
  
positive.code: :toc: left
  :source-language: java
  
  Data comes in many sizes, and saving all of your data in HBase, including binary data such as images and documents, is ideal. HBase can technically handle binary objects with cells that are up to 10MB in size. However, HBase's normal read and write paths are optimized for values smaller than 100KB in size. When HBase deals with large numbers of values up to 10MB, referred to here as medium objects, or MOBs, performance is degraded due to write amplification caused by splits and compactions. HBase ***FIX_VERSION_NUMBER*** adds support for better managing large numbers of MOBs while maintaining performance, consistency, and low operational overhead. MOB support is provided by the work done in link:https://issues.apache.org/jira/browse/HBASE-11339[HBASE-11339].
  
  To take advantage of MOB, you need to use <<hfilev3,HFile version 3>>. Optionally, configure the MOB file reader's cache settings for each RegionServer (see <<mob.cache.configure>>), then configure specific columns to hold MOB data.
  
  Client code does not need to change to take advantage of HBase MOB support. The feature is transparent to the client.
  
  === Configuring Columns for MOB
  
  You can configure columns to support MOB during table creation or alteration, either in HBase Shell or via the Java API. The two relevant properties are the boolean `IS_MOB` and the `MOB_THRESHOLD`, which is the number of bytes at which an object is considered to be a MOB. Only `IS_MOB` is required. If you do not specify the `MOB_THRESHOLD`, the default threshold value of 100 kb is used.
  
  .Configure a Column for MOB Using HBase Shell
  ====
  
negative.code:     <name>hbase.mob.cache.evict.period</name>
      <value>3600</value>
      <description>
        The amount of time in seconds after which an unused file is evicted from the
        MOB cache. The default value is 3600 seconds.
      </description>
  </property>
  <property>
      <name>hbase.mob.cache.evict.remain.ratio</name>
      <value>0.5f</value>
      <description>
        A multiplier (between 0.0 and 1.0), which determines how many files remain cached
        after the threshold of files that remains cached after a cache eviction occurs
        which is triggered by reaching the `hbase.mob.file.cache.size` threshold.
        The default value is 0.5f, which means that half the files (the least-recently-used
        ones) are evicted.
      </description>
  </property>
  ----
  