Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-25169 Update documentation about meta region replica (#2528) 

Signed-off-by: Michael Stack <stack@apache.org>
This commit is contained in:
Duo Zhang 2020-10-13 09:44:18 +08:00 committed by GitHub
parent 92c3bcd9fb
commit b186c51796
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/main/asciidoc/_chapters/architecture.adoc
View File

@ -2753,8 +2753,6 @@ See the above HDFS Architecture link for more information.
[[arch.timelineconsistent.reads]] [[arch.timelineconsistent.reads]]
== Timeline-consistent High Available Reads == Timeline-consistent High Available Reads
NOTE: The current <<amv2, Assignment Manager V2>> does not work well with region replica, so this feature maybe broken. Use it with caution.
[[casestudies.timelineconsistent.intro]] [[casestudies.timelineconsistent.intro]]
=== Introduction === Introduction
@ -2920,7 +2918,7 @@ Instead you can change the number of region replicas per table to increase or de
<name>hbase.regionserver.meta.storefile.refresh.period</name> <name>hbase.regionserver.meta.storefile.refresh.period</name>
<value>300000</value> <value>300000</value>
<description> <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). 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.
</description> </description>
</property> </property>
@ -2953,15 +2951,6 @@ Instead you can change the number of region replicas per table to increase or de
The period (in milliseconds) to keep store files in the archive folder before deleting them from the file system.</description> The period (in milliseconds) to keep store files in the archive folder before deleting them from the file system.</description>
</property> </property>
<property>
<name>hbase.meta.replica.count</name>
<value>3</value>
<description>
Region replication count for the meta regions. Defaults to 1.
</description>
</property>
<property> <property>
<name>hbase.region.replica.storefile.refresh.memstore.multiplier</name> <name>hbase.region.replica.storefile.refresh.memstore.multiplier</name>
<value>4</value> <value>4</value>