安装CM的hbase插件时遇到报错,Server Monitor未找到活动的Master?报错-问答-阿里云开发者社区-阿里云

开发者社区> 问答> 正文

安装CM的hbase插件时遇到报错,Server Monitor未找到活动的Master?报错

爱吃鱼的程序员 2020-06-07 16:45:53 40

报错信息如下:

#cd /var/log/hbase/
#tail -100 hbase-cmf-hbase-MASTER-hadoop2.log.out

2018-04-28 04:01:48,978 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown.
org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /hbase/.tmp/hbase.version could only be replicated to 0 nodes instead of minReplication (=1).  There are 4 datanode(s) running and no node(s) are excluded in this operation.    
    at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:1720)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:3389)
    at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:683)
    at org.apache.hadoop.hdfs.server.namenode.AuthorizationProviderProxyClientProtocol.addBlock(AuthorizationProviderProxyClientProtocol.java:214)
    at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:495)
    at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
    at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617)
    at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1073)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2217)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2213)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:422)
    at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1917)
    at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2211)

    at org.apache.hadoop.ipc.Client.call(Client.java:1504)
    at org.apache.hadoop.ipc.Client.call(Client.java:1441)
    at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:230)
    at com.sun.proxy.$Proxy21.addBlock(Unknown Source)
    at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:413)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:258)
    at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:104)
    at com.sun.proxy.$Proxy22.addBlock(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.apache.hadoop.hbase.fs.HFileSystem$1.invoke(HFileSystem.java:283)
    at com.sun.proxy.$Proxy23.addBlock(Unknown Source)
    at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1814)
    at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1610)
    at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:773)
2018-04-28 04:01:48,979 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: STOPPED: Unhandled exception. Starting shutdown.
2018-04-28 04:01:51,695 INFO org.apache.hadoop.hbase.ipc.RpcServer: Stopping server on 60000
2018-04-28 04:01:51,696 INFO org.apache.hadoop.hbase.ipc.RpcServer: RpcServer.listener,port=60000: stopping
2018-04-28 04:01:51,698 INFO org.apache.hadoop.hbase.ipc.RpcServer: RpcServer.responder: stopped
2018-04-28 04:01:51,698 INFO org.apache.hadoop.hbase.ipc.RpcServer: RpcServer.responder: stopping
2018-04-28 04:01:51,698 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: Stopping infoServer
2018-04-28 04:01:51,715 INFO org.mortbay.log: Stopped SelectChannelConnector@0.0.0.0:60010
2018-04-28 04:01:51,720 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: stopping server hadoop2,60000,1524902443457
2018-04-28 04:01:51,720 INFO org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x2630b1856b2007c
2018-04-28 04:01:51,724 INFO org.apache.zookeeper.ZooKeeper: Session: 0x2630b1856b2007c closed
2018-04-28 04:01:51,724 INFO org.apache.zookeeper.ClientCnxn: EventThread shut down
2018-04-28 04:01:51,725 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: stopping server hadoop2,60000,1524902443457; all regions closed.
2018-04-28 04:01:51,725 INFO org.apache.hadoop.hbase.ChoreService: Chore service for: hadoop2,60000,1524902443457 had [] on shutdown 2018-04-28 04:01:51,729 INFO org.apache.hadoop.hbase.ipc.RpcServer: Stopping server on 60000 2018-04-28 04:01:51,734 INFO org.apache.zookeeper.ZooKeeper: Session: 0x3630b1856da0089 closed 2018-04-28 04:01:51,734 INFO org.apache.zookeeper.ClientCnxn: EventThread shut down 2018-04-28 04:01:51,735 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: stopping server hadoop2,60000,1524902443457; zookeeper connection closed. 2018-04-28 04:01:51,735 INFO org.apache.hadoop.hbase.regionserver.HRegionServer: master/hadoop2/10.32.156.82:60000 exiting. 

[root@hadoop2 /]# jps
17891 NameNode
28198 Jps
17862 DFSZKFailoverController
17864 DataNode
18392 NodeManager
18505 HRegionServer
18442 ResourceManager

DataNode显示已经启动

以下时CM界面显示的报错:

不良 : Master 汇总: hadoop2(可用性:未知,运行状况:不良), hadoop3(可用性:未知,运行状况:不良). 该运行状况测试不良,因为 Service Monitor 未找到活动 Master。

分布式计算 Hadoop 分布式数据库 Hbase
分享到
取消 提交回答
全部回答(1)
  • 爱吃鱼的程序员
    2020-06-07 16:46:12
                        <pre><code>2018-05-01 04:08:47,569 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0xb1fb630ac48ab741,  containing 1 storage report(s), of which we sent 1. The reports had 0 total blo
    

    cks and used 1 RPC(s). This took 0 msec to generate and 2 msecs for RPC and NN processing. Got back one command: FinalizeCommand/5.2018-05-01 04:08:47,569 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Got finalize command for block pool BP-1717835256-10.32.156.82-1524104542738 2018-05-01 04:48:23,373 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0x810b1ee41f9a3ed9, containing 1 storage report(s), of which we sent 1. The reports had 0 total blo cks and used 1 RPC(s). This took 0 msec to generate and 2 msecs for RPC and NN processing. Got back no commands.2018-05-01 07:14:43,750 INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: BlockPool BP-1717835256-10.32.156.82-1524104542738 Total blocks: 0, missing metadata files:0, missing block files:0, missin g blocks in memory:0, mismatched blocks:02018-05-01 10:08:48,634 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0xb1fb630ac48ab742, containing 1 storage report(s), of which we sent 1. The reports had 0 total blo cks and used 1 RPC(s). This took 0 msec to generate and 1 msecs for RPC and NN processing. Got back one command: FinalizeCommand/5.2018-05-01 10:08:48,634 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Got finalize command for block pool BP-1717835256-10.32.156.82-1524104542738 2018-05-01 10:48:24,485 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0x810b1ee41f9a3eda, containing 1 storage report(s), of which we sent 1. The reports had 0 total blo cks and used 1 RPC(s). This took 1 msec to generate and 1 msecs for RPC and NN processing. Got back no commands.2018-05-01 13:14:43,749 INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: BlockPool BP-1717835256-10.32.156.82-1524104542738 Total blocks: 0, missing metadata files:0, missing block files:0, missin g blocks in memory:0, mismatched blocks:02018-05-01 16:08:46,679 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0xb1fb630ac48ab743, containing 1 storage report(s), of which we sent 1. The reports had 0 total blo cks and used 1 RPC(s). This took 0 msec to generate and 1 msecs for RPC and NN processing. Got back one command: FinalizeCommand/5.2018-05-01 16:08:46,680 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Got finalize command for block pool BP-1717835256-10.32.156.82-1524104542738 2018-05-01 16:48:22,431 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0x810b1ee41f9a3edb, containing 1 storage report(s), of which we sent 1. The reports had 0 total blo cks and used 1 RPC(s). This took 0 msec to generate and 2 msecs for RPC and NN processing. Got back no commands.2018-05-01 19:14:43,750 INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: BlockPool BP-1717835256-10.32.156.82-1524104542738 Total blocks: 0, missing metadata files:0, missing block files:0, missin g blocks in memory:0, mismatched blocks:0

    这是DataNode的日志信息,DataNode

                        <p>同样的问题,哪位大佬解决一下</p>
    
    0 0
数据库
使用钉钉扫一扫加入圈子
+ 订阅

分享数据库前沿,解构实战干货,推动数据库技术变革

推荐文章
相似问题
推荐课程