简介:HRegionServer定期心跳,给HMaster发送消息。RegionLoad会随心跳发送到HMaster。可以使用HBaseAdmin.getClusterStatus获取cluster状态信息,其中包含了所有region的RegionLoad信息。
RegionLoad中目前包以下信息:
setRegionSpecifier(regionSpecifier.build())
.setStores(stores)
.setStorefiles(storefiles)
.setStoreUncompressedSizeMB(storeUncompressedSizeMB)
.setStorefileSizeMB(storefileSizeMB)
.setMemstoreSizeMB(memstoreSizeMB)
.setStorefileIndexSizeMB(storefileIndexSizeMB)
.setRootIndexSizeKB(rootIndexSizeKB)
.setTotalStaticIndexSizeKB(totalStaticIndexSizeKB)
.setTotalStaticBloomSizeKB(totalStaticBloomSizeKB)
.setReadRequestsCount(r.readRequestsCount.get())
.setWriteRequestsCount(r.writeRequestsCount.get())
.setTotalCompactingKVs(totalCompactingKVs)
.setCurrentCompactedKVs(currentCompactedKVs)
.setCompleteSequenceId(r.completeSequenceId)
.setDataLocality(dataLocality)
HBase RegionLoad的使用:
1.RegionLoad的初始化在HRegionServer的createRegionLoad方法中
2.regionserver的心跳:HRegionserver.run()–>HRegionserver.tryRegionServerReport–>HRegionserver.buildServerLoad–>HRegionserver.createRegionLoad()
3.HBaseAdmin:
ClusterStatus status = admin.getClusterStatus();
for (ServerName sn : status.getServers())
for (Map.Entry < byte[], RegionLoad> entry : status.getLoad(sn).getRegionsLoad().entrySet())
status.getLoad内部实现:
public ServerLoad getLoad(final ServerName sn) {
return this.liveServers.get(sn);
}
3.HMaster端:HMaster.getClusterStatus<–>HBaseAdmin
HMaster.regionServerReport<–>HRegionserver
看一下liveServers是怎么被赋值的:
查看liveServers的调用,可以看到这个对象是ClusterStatus初始化的时候赋值的。
ClusterStatus初始化是在HMaster的 public ClusterStatus getClusterStatus()方法最后
liveServers实际对应的是HMaster的this.serverManager.getOnlineServers()
看一下什么地方更新了onlineServer:
有两个方法:
recordNewServerWithLock
regionServerReport<–HMaster.regionServerReport(regionserver心跳)<–HRegionServer.tryRegionServerReport<–HRegionserver.run()中间隔msgInterval调用一次
this.msgInterval = conf.getInt(“hbase.regionserver.msginterval”, 3 * 1000);
其他相关类:
ServerManager:
如果要在RegionLoad中增加要传输的数据:
1.ClusterStatus.proto中message RegionLoad增加参数
2.在HRegionServer的createRegionLoad方法中set对应的数据