HBASE-15305 Fix a couple of incorrect anchors in HBase Ref Guide
This commit is contained in:
parent
12813c7f03
commit
6462a615cb
|
@ -1032,6 +1032,7 @@ For background, see link:https://issues.apache.org/jira/browse/HBASE-2643[HBASE-
|
|||
|
||||
WAL log splitting and recovery can be resource intensive and take a long time, depending on the number of RegionServers involved in the crash and the size of the regions. <<distributed.log.splitting>> was developed to improve performance during log splitting.
|
||||
|
||||
[[distributed.log.splitting]]
|
||||
.Enabling or Disabling Distributed Log Splitting
|
||||
|
||||
Distributed log processing is enabled by default since HBase 0.92.
|
||||
|
|
|
@ -770,14 +770,6 @@ 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.
|
||||
|
||||
[[backup.master.fail.fast]]
|
||||
==== If a backup Master exists, make the primary Master fail fast
|
||||
|
||||
If the primary Master loses its connection with ZooKeeper, it will fall into a loop where it keeps trying to reconnect.
|
||||
Disable this functionality if you are running more than one Master: i.e. a backup Master.
|
||||
Failing to do so, the dying Master may continue to receive RPCs though another Master has assumed the role of primary.
|
||||
See the configuration <<fail.fast.expired.active.master,fail.fast.expired.active.master>>.
|
||||
|
||||
[[recommended_configurations]]
|
||||
=== Recommended Configurations
|
||||
|
||||
|
|
Loading…
Reference in New Issue