anchor.diff:  
   You can also use `setRegionReplication()` and alter table to increase, decrease the region replication for a table.
   
  -=== Region splits and merges
  -
  -Region splits and merges are not compatible with regions with replicas yet.
  -So you have to pre-split the table, and disable the region splits.
  -Also you should not execute region merges on tables with region replicas.
  -To disable region splits you can use DisabledRegionSplitPolicy as the split policy.
  -
  -=== User Interface
  -
  -In the masters user interface, the region replicas of a table are also shown together with the primary regions.
  -You can notice that the replicas of a region will share the same start and end keys and the same region name prefix.
  -The only difference would be the appended replica_id (which is encoded as hex), and the region encoded name will be different.
  -You can also see the replica ids shown explicitly in the UI.
  -
  -=== API and Usage
  +
  +=== Read API and Usage
   
   ==== Shell
   
  
positive.code: ResultScanner scanner = table.getScanner(scan);
  ----
  
  You can inspect whether the results are coming from primary region or not by calling the Result.isStale() method:
  
  [source,java]
  ----
  
negative.code: [source,xml]
  ----
  <property>
      <name>hbase.regionserver.storefile.refresh.period</name>
      <value>0</value>
      <description>
        The period (in milliseconds) for refreshing the store files for the secondary regions. 0 means this feature is disabled. Secondary regions sees new files (from flushes and compactions) from primary once the secondary region refreshes the list of files in the region (there is no notification mechanism). But too frequent refreshes might cause extra Namenode pressure. If the files cannot be refreshed for longer than HFile TTL (hbase.master.hfilecleaner.ttl) the requests are rejected. Configuring HFile TTL to a larger value is also recommended with this setting.
      </description>
  </property>
  
  <property>
      <name>hbase.regionserver.meta.storefile.refresh.period</name>
      <value>300000</value>
      <description>
        The period (in milliseconds) for refreshing the store files for the hbase:meta tables secondary regions. 0 means this feature is disabled. Secondary regions sees new files (from flushes and compactions) from primary once the secondary region refreshes the list of files in the region (there is no notification mechanism). But too frequent refreshes might cause extra Namenode pressure. If the files cannot be refreshed for longer than HFile TTL (hbase.master.hfilecleaner.ttl) the requests are rejected. Configuring HFile TTL to a larger value is also recommended with this setting. This should be a non-zero number if meta replicas are enabled (via hbase.meta.replica.count set to greater than 1).
      </description>
  </property>
  
  <property>
      <name>hbase.region.replica.replication.enabled</name>
      <value>true</value>
      <description>
        Whether asynchronous WAL replication to the secondary region replicas is enabled or not. If this is enabled, a replication peer named "region_replica_replication" will be created which will tail the logs and replicate the mutatations to region replicas for tables that have region replication > 1. If this is enabled once, disabling this replication also      requires disabling the replication peer using shell or ReplicationAdmin java class. Replication to secondary region replicas works over standard inter-cluster replication. So replication, if disabled explicitly, also has to be enabled by setting "hbase.replication"· to true for this feature to work.
      </description>
  </property>
  <property>
    <name>hbase.region.replica.replication.memstore.enabled</name>
  