(错误)HBase启动HMaster和HRegionserve冲突 regionserver.HRegionServerCommandLine: Region server exiting

本文介绍了在HBase单机伪分布式环境中遇到的HRegionServer和HMaster端口冲突问题,详细解析了错误日志,并提供了修改配置文件解决端口冲突的方法。

【问题描述】

今天在搭建的HBase单机伪分布式集群环境上运行start-hbase.sh来启动Hbase,使用jps命令查看进程:

10195 Jps

9237 JobHistoryServer

9669 HMaster

8839 ResourceManager

9080 NodeManager

9608 HQuorumPeer

8457 DataNode

8300 NameNode

8652 SecondaryNameNode

其中HMaster,HRegionServer是HBase的进程,但是HRegionServer进程没有启动成功;

重新stop-hbase.sh再启动后,查看进程:

10195 Jps

9237 JobHistoryServer

8839 ResourceManager

9847 HRegionServer

9080 NodeManager

9608 HQuorumPeer

8457 DataNode

8300 NameNode

8652 SecondaryNameNode

又变成HMaster进程无法启动成功。

通过http://192.168.40.199:16010查看HMaster Web管理页面,RegionServers内容也为空白,确认为RegionServers进程因为16020端口占用而启动失败问题。

查看HRegionServer启动失败的日志文件(hbase-liurong-regionserver-hadoop.log),错误信息如下:

2021-03-17 11:20:07,292 ERROR [main] regionserver.HRegionServerCommandLine: Region server exiting
java.lang.RuntimeException: Failed construction of Regionserver: class org.apache.hadoop.hbase.regionserver.HRegionServer
    at org.apache.hadoop.hbase.regionserver.HRegionServer.constructRegionServer(HRegionServer.java:2496)
    at org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.start(HRegionServerCommandLine.java:64)
    at org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.run(HRegionServerCommandLine.java:87)
    at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
    at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
    at org.apache.hadoop.hbase.regionserver.HRegionServer.main(HRegionServer.java:2511)
Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.apache.hadoop.hbase.regionserver.HRegionServer.constructRegionServer(HRegionServer.java:2494)
    ... 5 more
Caused by: java.net.BindException: Problem binding to hadoop/192.168.40.199:16020 : 地址已在使用
    at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2371)
    at org.apache.hadoop.hbase.ipc.RpcServer$Listener.<init>(RpcServer.java:524)
    at org.apache.hadoop.hbase.ipc.RpcServer.<init>(RpcServer.java:1899)
    at org.apache.hadoop.hbase.regionserver.RSRpcServices.<init>(RSRpcServices.java:792)
    at org.apache.hadoop.hbase.regionserver.HRegionServer.createRpcServices(HRegionServer.java:575)
    at org.apache.hadoop.hbase.regionserver.HRegionServer.<init>(HRegionServer.java:492)
    ... 10 more
Caused by: java.net.BindException: 地址已在使用
    at sun.nio.ch.Net.bind0(Native Method)
    at sun.nio.ch.Net.bind(Net.java:444)
    at sun.nio.ch.Net.bind(Net.java:436)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
    at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2369)
    ... 15 more

【错误原因】

在hbase升级到1.0.0版本后,默认端口做了改动。其中16020端口是HMaster和HRegionServer服务各自使用的默认端口,导致端口冲突,一旦某一个端口先启动,则另一个端口启动出现了冲突无法启动成功。官方文档信息如下:

The HMaster server controls the HBase cluster. You can start up to 9 backup HMaster servers, which makes 10 total HMasters, counting the primary. To start a backup HMaster, use the local-master-backup.sh. For each backup   master you want to start, add a parameter representing the port offset for that master. Each HMaster uses three ports (16010, 16020, and 16030 by default). The port offset is added to these ports, so using an offset of 2, the   backup HMaster would use ports 16012, 16022, and 16032. The following command starts 3 backup servers using ports 16012/16022/16032, 16013/16023/16033, and 16015/16025/16035.

  The HRegionServer manages the data in its StoreFiles as directed by the HMaster. Generally, one HRegionServer runs per node in the cluster. Running multiple HRegionServers on the same system can be useful for testing in

  pseudo-distributed mode. The local-regionservers.sh command allows you to run multiple RegionServers. It works in a similar way to the local-master-backup.sh command, in that each parameter you provide represents the port offset for an instance. Each RegionServer requires two ports, and the default ports are 16020 and 16030. However, the base ports for additional RegionServers are not the default ports since the default ports are used by the HMaster, which is also a RegionServer since HBase version 1.0.0. The base ports are 16200 and 16300 instead. You can run 99 additional RegionServers that are not a HMaster or backup HMaster, on a server. The following command starts four additional RegionServers, running on sequential ports starting at 16202/16302 (base ports 16200/16300 plus 2).

【解决办法】

既然是端口冲突,按理说修改RegionServer相关的配置可以解决该问题。这里通过定义自己的端口配置来解决该问题。

修改hbase配置文件/conf/hbase-site.xml

在<configuration></configuration>标签内添加下面配置:

<!--HBase的Master的端口,默认16000-->
<property>
	<name>hbase.master.port</name>
	<value>16000</value>
</property>
<!--HBase Master web界面端口,默认是16010-->
<property>
	<name>hbase.master.info.port</name>
	<value>16010</value>
</property>
<!--HBase RegionServer绑定的端口,默认16020-->
<!--改成16201-->
<property>
	<name>hbase.regionserver.port</name>
	<value>16201</value>
</property>
<!--HBase RegionServer web 界面绑定的端口,默认是16030-->
<!--改成16301-->
<property>
	<name>hbase.regionserver.info.port</name>
	<value>16301</value>
</property>

再重新停止启动HBase,查看进程启动情况

9237 JobHistoryServer

9669 HMaster

8839 ResourceManager

9847 HRegionServer

9080 NodeManager

9608 HQuorumPeer

10680 Jps

8457 DataNode

8300 NameNode

8652 SecondaryNameNode

已经可以正常启动。

方案补充:如果使用start-hbase.sh脚本启动regionserver还是会报端口冲突问题,可以通过使用单独的regionserver脚本启动HRegionServer来规避。

[bin]$ local-regionservers.sh start 1(2,3,4)

(1,2,3,4表示偏移量 默认端口是16020 加上偏移量之后启用16021端口,解决端口冲突)

参考:

hbase Problem binding to node1/192.168.1.13:16020 : 地址已在使用 - 新际航 - 博客园

base/MasterData/oldWALs, maxLogs=10 2025-06-24 21:56:39,697 INFO [master/hadoop102:16000:becomeActiveMaster] wal.AbstractFSWAL: Closed WAL: AsyncFSWAL hadoop102%2C16000%2C1750773392926:(num 1750773399658) 2025-06-24 21:56:39,701 ERROR [master/hadoop102:16000:becomeActiveMaster] master.HMaster: Failed to become active master java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623) at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53) at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190) at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160) at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:719) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:884) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:577) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:518) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62) at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295) at org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200) at org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:263) at org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:344) at org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:856) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2199) at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:529) at java.lang.Thread.run(Thread.java:750) 2025-06-24 21:56:39,702 ERROR [master/hadoop102:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master hadoop102,16000,1750773392926: Unhandled exception. Starting shutdown. ***** java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623) at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53) at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190) at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160) at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:719) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:884) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:577) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:518) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62) at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295) at org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200) at org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:263) at org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:344) at org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:856) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2199) at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:529) at java.lang.Thread.run(Thread.java:750) 2025-06-24 21:56:39,703 INFO [master/hadoop102:16000:becomeActiveMaster] regionserver.HRegionServer: ***** STOPPING region server 'hadoop102,16000,1750773392926' ***** 2025-06-24 21:56:39,703 INFO [master/hadoop102:16000:becomeActiveMaster] regionserver.HRegionServer: STOPPED: Stopped by master/hadoop102:16000:becomeActiveMaster 2025-06-24 21:56:40,607 INFO [master/hadoop102:16000] ipc.NettyRpcServer: Stopping server on /192.168.10.102:16000 2025-06-24 21:56:40,628 INFO [master/hadoop102:16000] regionserver.HRegionServer: Stopping infoServer 2025-06-24 21:56:40,652 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.w.WebAppContext@45acdd11{master,/,null,STOPPED}{file:/opt/module/hbase-2.4.18/hbase-webapps/master} 2025-06-24 21:56:40,658 INFO [master/hadoop102:16000] server.AbstractConnector: Stopped ServerConnector@7efd28bd{HTTP/1.1, (http/1.1)}{0.0.0.0:16010} 2025-06-24 21:56:40,659 INFO [master/hadoop102:16000] server.session: node0 Stopped scavenging 2025-06-24 21:56:40,659 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.s.ServletContextHandler@5f7da3d3{static,/static,file:///opt/module/hbase-2.4.18/hbase-webapps/static/,STOPPED} 2025-06-24 21:56:40,660 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.s.ServletContextHandler@2b10ace9{logs,/logs,file:///opt/module/hbase-2.4.18/logs/,STOPPED} 2025-06-24 21:56:40,664 INFO [master/hadoop102:16000] regionserver.HRegionServer: aborting server hadoop102,16000,1750773392926 2025-06-24 21:56:40,665 INFO [master/hadoop102:16000] regionserver.HRegionServer: stopping server hadoop102,16000,1750773392926; all regions closed. 2025-06-24 21:56:40,665 INFO [master/hadoop102:16000] hbase.ChoreService: Chore service for: master/hadoop102:16000 had [] on shutdown 2025-06-24 21:56:40,672 WARN [master/hadoop102:16000] master.ActiveMasterManager: Failed get of master address: java.io.IOException: Can't get master address from ZooKeeper; znode data == null 2025-06-24 21:56:40,782 INFO [ReadOnlyZKClient-hadoop102:2181,hadoop103:2181,hadoop104:2181@0x1a9293ba] zookeeper.ZooKeeper: Session: 0x20000754c8c0002 closed 2025-06-24 21:56:40,782 INFO [ReadOnlyZKClient-hadoop102:2181,hadoop103:2181,hadoop104:2181@0x1a9293ba-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x20000754c8c0002 2025-06-24 21:56:40,797 INFO [master/hadoop102:16000] zookeeper.ZooKeeper: Session: 0x100007708c00000 closed 2025-06-24 21:56:40,797 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x100007708c00000 2025-06-24 21:56:40,797 INFO [master/hadoop102:16000] regionserver.HRegionServer: Exiting; stopping=hadoop102,16000,1750773392926; zookeeper connection closed. 2025-06-24 21:56:40,798 ERROR [main] master.HMasterCommandLine: Master exiting java.lang.RuntimeException: HMaster Aborted at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:254) at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:145) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:82) at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:140) at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2969) [manager1@hadoop102 logs]$
06-25
HMASTER日志报错2025-11-13 17:30:58,132 INFO [sxs1:16000.activeMasterManager] procedure.ZKProcedureUtil: Clearing all procedure znodes: /hbase/flush-table-proc/acquired /hbase/flush-table-proc/reached /hbase/flush-table-proc/abort 2025-11-13 17:30:58,139 INFO [sxs1:16000.activeMasterManager] procedure.ZKProcedureUtil: Clearing all procedure znodes: /hbase/online-snapshot/acquired /hbase/online-snapshot/reached /hbase/online-snapshot/abort 2025-11-13 17:30:58,152 INFO [sxs1:16000.activeMasterManager] master.MasterCoprocessorHost: System coprocessor loading is enabled 2025-11-13 17:30:58,160 INFO [sxs1:16000.activeMasterManager] procedure2.ProcedureExecutor: Starting procedure executor threads=5 2025-11-13 17:30:58,160 INFO [sxs1:16000.activeMasterManager] wal.WALProcedureStore: Starting WAL Procedure Store lease recovery 2025-11-13 17:30:58,164 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000006.log 2025-11-13 17:30:58,168 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000006.log after 3ms 2025-11-13 17:30:58,172 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000007.log 2025-11-13 17:30:58,173 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000007.log after 1ms 2025-11-13 17:30:58,177 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000008.log 2025-11-13 17:30:58,178 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000008.log after 1ms 2025-11-13 17:30:58,184 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000009.log 2025-11-13 17:30:58,188 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000009.log after 4ms 2025-11-13 17:30:58,193 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000010.log 2025-11-13 17:30:58,195 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000010.log after 2ms 2025-11-13 17:30:58,201 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000011.log 2025-11-13 17:30:58,201 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000011.log after 0ms 2025-11-13 17:30:58,205 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000012.log 2025-11-13 17:30:58,205 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000012.log after 0ms 2025-11-13 17:30:58,211 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000013.log 2025-11-13 17:30:58,212 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000013.log after 1ms 2025-11-13 17:30:58,215 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000014.log 2025-11-13 17:30:58,216 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000014.log after 1ms 2025-11-13 17:30:58,224 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recover lease on dfs file hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000015.log 2025-11-13 17:30:58,225 INFO [sxs1:16000.activeMasterManager] util.FSHDFSUtils: Recovered lease, attempt=0 on file=hdfs://sxs1:9000/hbase/MasterProcWALs/state-00000000000000000015.log after 1ms 2025-11-13 17:30:58,248 INFO [sxs1:16000.activeMasterManager] wal.WALProcedureStore: Lease acquired for flushLogId: 16 2025-11-13 17:30:58,256 INFO [sxs1:16000.activeMasterManager] zookeeper.RecoverableZooKeeper: Process identifier=replicationLogCleaner connecting to ZooKeeper ensemble=sxs1:2181,sxs2:2181,sxs3:2181 2025-11-13 17:30:58,268 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 0, slept for 0 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms. 2025-11-13 17:30:59,783 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 0, slept for 1515 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms. 2025-11-13 17:31:00,918 INFO [B.defaultRpcServer.handler=1,queue=1,port=16000] master.ServerManager: Registering server=sxs1,16020,1763025688227 2025-11-13 17:31:00,928 INFO [B.defaultRpcServer.handler=0,queue=0,port=16000] master.ServerManager: Registering server=sxs2,16020,1763024791986 2025-11-13 17:31:00,949 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 2, slept for 2681 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms. 2025-11-13 17:31:00,966 INFO [B.defaultRpcServer.handler=2,queue=2,port=16000] master.ServerManager: Registering server=sxs3,16020,1763024792019 2025-11-13 17:31:01,004 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 3, slept for 2736 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms. 2025-11-13 17:31:02,522 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 3, slept for 4254 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms. 2025-11-13 17:31:02,775 INFO [sxs1:16000.activeMasterManager] master.ServerManager: Finished waiting for region servers count to settle; checked in 3, slept for 4507 ms, expecting minimum of 1, maximum of 2147483647, master is running 2025-11-13 17:31:02,782 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs1,16020,1761034573023 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,790 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs1,16020,1762933906517 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,793 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs1,16020,1762938640637 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,793 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs1,16020,1762939757280 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,795 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs1,16020,1763025688227 belongs to an existing region server 2025-11-13 17:31:02,796 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1761034787828-splitting doesn't belong to a known region server, splitting 2025-11-13 17:31:02,797 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1762933902565 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,797 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1762937541819 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,799 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1762938639822 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,800 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1763024791986 belongs to an existing region server 2025-11-13 17:31:02,803 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs3,16020,1761034787825 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,805 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs3,16020,1762933904233 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,806 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs3,16020,1762937541854 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,807 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs3,16020,1762938639774 doesn't belong to a known region server, splitting 2025-11-13 17:31:02,808 INFO [sxs1:16000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://sxs1:9000/hbase/WALs/sxs3,16020,1763024792019 belongs to an existing region server 2025-11-13 17:31:02,814 INFO [sxs1:16000.activeMasterManager] master.SplitLogManager: dead splitlog workers [sxs2,16020,1761034787828] 2025-11-13 17:31:02,816 INFO [sxs1:16000.activeMasterManager] master.SplitLogManager: Started splitting 1 logs in [hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1761034787828-splitting] for [sxs2,16020,1761034787828] 2025-11-13 17:31:02,827 INFO [main-EventThread] coordination.SplitLogManagerCoordination: task /hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta acquired by sxs3,16020,1763024792019 2025-11-13 17:31:03,059 INFO [sxs1,16000,1763026256316_splitLogManager__ChoreService_1] master.SplitLogManager: total tasks = 1 unassigned = 0 tasks={/hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta=last_update = 1763026262876 last_version = 2 cur_worker_name = sxs3,16020,1763024792019 status = in_progress incarnation = 0 resubmits = 0 batch = installed = 1 done = 0 error = 0} 2025-11-13 17:31:09,058 INFO [sxs1,16000,1763026256316_splitLogManager__ChoreService_1] master.SplitLogManager: total tasks = 1 unassigned = 0 tasks={/hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta=last_update = 1763026262876 last_version = 2 cur_worker_name = sxs3,16020,1763024792019 status = in_progress incarnation = 0 resubmits = 0 batch = installed = 1 done = 0 error = 0} 2025-11-13 17:31:15,058 INFO [sxs1,16000,1763026256316_splitLogManager__ChoreService_1] master.SplitLogManager: total tasks = 1 unassigned = 0 tasks={/hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta=last_update = 1763026262876 last_version = 2 cur_worker_name = sxs3,16020,1763024792019 status = in_progress incarnation = 0 resubmits = 0 batch = installed = 1 done = 0 error = 0} 2025-11-13 17:31:18,634 INFO [main-EventThread] coordination.SplitLogManagerCoordination: task /hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta entered state: ERR sxs3,16020,1763024792019 2025-11-13 17:31:18,634 WARN [main-EventThread] coordination.SplitLogManagerCoordination: Error splitting /hbase/splitWAL/WALs%2Fsxs2%2C16020%2C1761034787828-splitting%2Fsxs2%252C16020%252C1761034787828..meta.1761038482217.meta 2025-11-13 17:31:18,635 WARN [sxs1:16000.activeMasterManager] master.SplitLogManager: error while splitting logs in [hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1761034787828-splitting] installed = 1 but only 0 done 2025-11-13 17:31:18,635 FATAL [sxs1:16000.activeMasterManager] master.HMaster: Failed to become active master java.io.IOException: error or interrupted while splitting logs in [hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1761034787828-splitting] Task = installed = 1 done = 0 error = 1 at org.apache.hadoop.hbase.master.SplitLogManager.splitLogDistributed(SplitLogManager.java:290) at org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:403) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:313) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:304) at org.apache.hadoop.hbase.master.HMaster.splitMetaLogBeforeAssignment(HMaster.java:1046) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:750) at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) at java.lang.Thread.run(Thread.java:745) 2025-11-13 17:31:18,636 FATAL [sxs1:16000.activeMasterManager] master.HMaster: Master server abort: loaded coprocessors are: [] 2025-11-13 17:31:18,636 FATAL [sxs1:16000.activeMasterManager] master.HMaster: Unhandled exception. Starting shutdown. java.io.IOException: error or interrupted while splitting logs in [hdfs://sxs1:9000/hbase/WALs/sxs2,16020,1761034787828-splitting] Task = installed = 1 done = 0 error = 1 at org.apache.hadoop.hbase.master.SplitLogManager.splitLogDistributed(SplitLogManager.java:290) at org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:403) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:313) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:304) at org.apache.hadoop.hbase.master.HMaster.splitMetaLogBeforeAssignment(HMaster.java:1046) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:750) at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) at java.lang.Thread.run(Thread.java:745) 2025-11-13 17:31:18,636 INFO [sxs1:16000.activeMasterManager] regionserver.HRegionServer: STOPPED: Unhandled exception. Starting shutdown. 2025-11-13 17:31:18,636 INFO [master/sxs1/192.168.78.100:16000] regionserver.HRegionServer: Stopping infoServer 2025-11-13 17:31:18,669 INFO [master/sxs1/192.168.78.100:16000] procedure2.ProcedureExecutor: Stopping the procedure executor 2025-11-13 17:31:18,669 INFO [master/sxs1/192.168.78.100:16000] wal.WALProcedureStore: Stopping the WAL Procedure Store 2025-11-13 17:31:18,776 INFO [master/sxs1/192.168.78.100:16000] regionserver.HRegionServer: stopping server sxs1,16000,1763026256316 2025-11-13 17:31:18,776 INFO [master/sxs1/192.168.78.100:16000] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x39a7c74c6a6000e 2025-11-13 17:31:18,778 INFO [master/sxs1/192.168.78.100:16000] regionserver.HRegionServer: stopping server sxs1,16000,1763026256316; all regions closed. 2025-11-13 17:31:18,779 INFO [master/sxs1/192.168.78.100:16000] hbase.ChoreService: Chore service for: sxs1,16000,1763026256316 had [[ScheduledChore: Name: HFileCleaner Period: 60000 Unit: MILLISECONDS], [ScheduledChore: Name: LogsCleaner Period: 60000 Unit: MILLISECONDS]] on shutdown 2025-11-13 17:31:18,782 INFO [master/sxs1/192.168.78.100:16000] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x29a7c74c6a30007 2025-11-13 17:31:18,785 INFO [master/sxs1/192.168.78.100:16000] hbase.ChoreService: Chore service for: sxs1,16000,1763026256316_splitLogManager_ had [[ScheduledChore: Name: SplitLogManager Timeout Monitor Period: 1000 Unit: MILLISECONDS]] on shutdown 2025-11-13 17:31:18,785 INFO [master/sxs1/192.168.78.100:16000] flush.MasterFlushTableProcedureManager: stop: server shutting down. 2025-11-13 17:31:18,785 INFO [master/sxs1/192.168.78.100:16000] ipc.RpcServer: Stopping server on 16000 2025-11-13 17:31:18,785 INFO [RpcServer.listener,port=16000] ipc.RpcServer: RpcServer.listener,port=16000: stopping 2025-11-13 17:31:18,786 INFO [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopped 2025-11-13 17:31:18,786 INFO [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopping 2025-11-13 17:31:18,794 INFO [master/sxs1/192.168.78.100:16000] regionserver.HRegionServer: stopping server sxs1,16000,1763026256316; zookeeper connection closed. 2025-11-13 17:31:18,794 INFO [master/sxs1/192.168.78.100:16000] regionserver.HRegionServer: master/sxs1/192.168.78.100:16000 exiting
最新发布
11-14
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值