重新启动hbase，可能存在Num.Regions = 0的情况，此问题仅出现在特定计算机上（可以确定为其他计算机占总磁盘的50％，占用率可比） 此过程没有例外，日志停留在：
2019-05-17 10:38:29,894 INFO [regionserver/gladslave3/10.86.10.103:16020] regionserver.ReplicationSourceManager: Current list of replicators: [gladslave4,16020,1558060698511, gladslave2,16020,1558060697919, gladslave3,16020,1558060700753, gladslave1,16020,1558060697694] other RSs: [gladslave4,16020,1558060698511, gladslave2,16020,1558060697919, gladslave3,16020,1558060700753, gladslave1,16020,1558060697694]
2019-05-17 10:38:29,936 INFO [SplitLogWorker-gladslave3:16020] regionserver.SplitLogWorker: SplitLogWorker gladslave3,16020,1558060700753 starting
2019-05-17 10:38:29,936 INFO [regionserver/gladslave3/10.86.10.103:16020] regionserver.HeapMemoryManager: Starting HeapMemoryTuner chore.
2019-05-17 10:38:29,939 INFO [regionserver/gladslave3/10.86.10.103:16020] regionserver.HRegionServer: Serving as gladslave3,16020,1558060700753, RpcServer on gladslave3/10.86.10.103:16020, sessionid=0x401e4be60870092
2019-05-17 10:38:30,467 INFO [regionserver/gladslave3/10.86.10.103:16020] quotas.RegionServerQuotaManager: Quota support disabled
2019-05-17 10:38:35,699 INFO [regionserver/gladslave3/10.86.10.103:16020] wal.FSHLog: WAL configuration: blocksize=128 MB, rollsize=121.60 MB, prefix=gladslave3%2C16020%2C1558060700753, suffix=, logDir=hdfs://haservice/hbase/WALs/gladslave3,16020,1558060700753, archiveDir=hdfs://haservice/hbase/oldWALs
2019-05-17 10:38:37,122 INFO [regionserver/gladslave3/10.86.10.103:16020] wal.FSHLog: Slow sync cost: 369 ms, current pipeline: []
2019-05-17 10:38:37,123 INFO [regionserver/gladslave3/10.86.10.103:16020] wal.FSHLog: New WAL /hbase/WALs/gladslave3,16020,1558060700753/gladslave3%2C16020%2C1558060700753.1558060715708
vi log4j.properties :g/INFO/s//DEBUG/G
重新启动测试20次，并且奇迹般地起作用了。没有Num.Regions = 0，但是区域的数量每次都会改变，它的分布几乎是均匀的
HBASE1.4.9每次启动时是否自动平衡？
生成环境日志级别至少为WARN。
如何解决Num.Regions = 0的问题？