anchor.diff:  [[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
  +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.
   
  
positive.code: </configuration>
  ----
  
  This is an example _conf/regionservers_ file, which contains a list of nodes that should run a RegionServer in the cluster.
  These nodes need HBase installed and they need to use the same contents of the _conf/_ directory as the Master server
  
  [source]
  ----
  
negative.code: [[hbase_env]]
  ==== _hbase-env.sh_
  
  The following lines in the _hbase-env.sh_ file show how to set the `JAVA_HOME` environment variable
  (required for HBase) and set the heap to 4 GB (rather than the default value of 1 GB). If you copy
  and paste this example, be sure to adjust the `JAVA_HOME` to suit your environment.
  
  ----
  # The java implementation to use.
  