@@ -606,8 +606,7 @@ possible configurations would overwhelm and obscure the important.
606606 Then the cluster's availability is at least 99% when balancing.</description >
607607 </property >
608608 <property >
609- <name >hbase.balancer.period
610- </name >
609+ <name >hbase.balancer.period</name >
611610 <value >300000</value >
612611 <description >Period at which the region balancer runs in the Master.</description >
613612 </property >
@@ -631,8 +630,27 @@ possible configurations would overwhelm and obscure the important.
631630 <property >
632631 <name >hbase.server.thread.wakefrequency</name >
633632 <value >10000</value >
634- <description >Time to sleep in between searches for work (in milliseconds).
635- Used as sleep interval by service threads such as log roller.</description >
633+ <description >In master side, this config is the period used for FS related behaviors:
634+ checking if hdfs is out of safe mode, setting or checking hbase.version file,
635+ setting or checking hbase.id file. Using default value should be fine.
636+ In regionserver side, this config is used in several places: flushing check interval,
637+ compaction check interval, wal rolling check interval. Specially, admin can tune
638+ flushing and compaction check interval by hbase.regionserver.flush.check.period
639+ and hbase.regionserver.compaction.check.period. (in milliseconds)</description >
640+ </property >
641+ <property >
642+ <name >hbase.regionserver.flush.check.period</name >
643+ <value >${hbase.server.thread.wakefrequency}</value >
644+ <description >It determines the flushing check period of PeriodicFlusher in regionserver.
645+ If unset, it uses hbase.server.thread.wakefrequency as default value.
646+ (in milliseconds)</description >
647+ </property >
648+ <property >
649+ <name >hbase.regionserver.compaction.check.period</name >
650+ <value >${hbase.server.thread.wakefrequency}</value >
651+ <description >It determines the compaction check period of CompactionChecker in regionserver.
652+ If unset, it uses hbase.server.thread.wakefrequency as default value.
653+ (in milliseconds)</description >
636654 </property >
637655 <property >
638656 <name >hbase.server.versionfile.writeattempts</name >
0 commit comments