anchor.diff:  </property>
   ----
   
  -And on the NameNode/DataNode side, set the following to enable 'staleness' introduced in HDFS-3703, HDFS-3912.
  +And on the NameNode/DataNode side, set the following to enable 'staleness' introduced in HDFS-3703,
  +HDFS-3912.
   
   [source,xml]
   ----
  
positive.code: node-c.example.com
  ----
  
  This is an example _conf/backup-masters_ file, which contains a list of each node that should run a backup Master instance.
  The backup Master instances will sit idle unless the main Master becomes unavailable.
  
  [source]
  ----
  
negative.code: [[big.cluster.config]]
  ==== Big Cluster Configurations
  
  If you have a cluster with a lot of regions, it is possible that a Regionserver checks in briefly
  after the Master starts while all the remaining RegionServers lag behind. This first server to
  check in will be assigned all regions which is not optimal. To prevent the above scenario from
  happening, up the `hbase.master.wait.on.regionservers.mintostart` property from its default value
  of 1. See link:https://issues.apache.org/jira/browse/HBASE-6389[HBASE-6389 Modify the
              conditions to ensure that Master waits for sufficient number of Region Servers before
              starting region assignments] for more detail.
  
  