anchor.diff:  [source,xml]
   ----
   <property>
  -  <name>hbase.ipc.client.allowsInterrupt</name>
  -  <value>true</value>
  -  <description>
  -    Whether to enable interruption of RPC threads at the client side. This is required for region replicas with fallback RPC’s to secondary regions.
  -  </description>
  +    <name>hbase.ipc.client.specificThreadForWriting</name>
  +    <value>true</value>
  +    <description>
  +      Whether to enable interruption of RPC threads at the client side. This is required for region replicas with fallback RPC’s to secondary regions.
  +    </description>
   </property>
   <property>
     <name>hbase.client.primaryCallTimeout.get</name>
  
positive.code: 
  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
  
  ==== Shell
  
  
negative.code:     The timeout (in microseconds), before secondary fallback RPC’s are submitted for scan requests with Consistency.TIMELINE to the secondary replicas of the regions. Defaults to 1 sec. Setting this lower will increase the number of RPC’s, but will lower the p99 latencies.
    </description>
  </property>
  <property>
      <name>hbase.meta.replicas.use</name>
      <value>true</value>
      <description>
        Whether to use meta table replicas or not. Default is false.
      </description>
  </property>
  ----
  
  Note HBase-1.0.x users should use `hbase.ipc.client.allowsInterrupt` rather than `hbase.ipc.client.specificThreadForWriting`. 
  
  === 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.
  
  === Creating a table with region replication
  
  Region replication is a per-table property.
  All tables have `REGION_REPLICATION = 1` by default, which means that there is only one replica per region.
  You can set and change the number of replicas per region of a table by supplying the `REGION_REPLICATION` property in the table descriptor.
  
  
  ==== Shell
  