anchor.diff:        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 mutations 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 Admin java class. Replication to secondary region replicas works over standard inter-cluster replication.
       </description>
   </property>
  -<property>
  -  <name>hbase.region.replica.replication.memstore.enabled</name>
  -  <value>true</value>
  -  <description>
  -    If you set this to `false`, replicas do not receive memstore updates from
  -    the primary RegionServer. If you set this to `true`, you can still disable
  -    memstore replication on a per-table basis, by setting the table's
  -    `REGION_MEMSTORE_REPLICATION` configuration property to `false`. If
  -    memstore replication is disabled, the secondaries will only receive
  -    updates for events like flushes and bulkloads, and will not have access to
  -    data which the primary has not yet flushed. This preserves the guarantee
  -    of row-level consistency, even when the read requests `Consistency.TIMELINE`.
  -  </description>
  -</property>
   
   <property>
       <name>hbase.master.hfilecleaner.ttl</name>
  
positive.code: 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
  
  
negative.code:  <name>hbase.region.replica.wait.for.primary.flush</name>
      <value>true</value>
      <description>
        Whether to wait for observing a full flush cycle from the primary before start serving data in a secondary. Disabling this might cause the secondary region replicas to go back in time for reads between region movements.Please note that if you set per-table property `REGION_MEMSTORE_REPLICATION` to false,`hbase.region.replica.wait.for.primary.flush` will be ignored.
      </description>
  </property>
  ----
  