`
ssydxa219
  • 浏览: 626266 次
  • 性别: Icon_minigender_1
  • 来自: 杭州
文章分类
社区版块
存档分类
最新评论

hbase 出现的问题

 
阅读更多

log4j:WARN No appenders could be found for logger (org.apache.hadoop.util.Shell).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Exception in thread "main" org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=36, exceptions:
Fri Jun 12 12:00:57 CST 2015, null, java.net.SocketTimeoutException: callTimeout=60000, callDuration=71425: row 'mytown:blog,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise06,60020,1434081500945, seqNum=0

    at org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedException(RpcRetryingCallerWithReadReplicas.java:264)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:215)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
    at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:288)
    at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:267)
    at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:139)
    at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:134)
    at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:825)
    at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:601)
    at org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:365)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:291)
    at org.zjenterprise.tizr.hbase.HBaseOperation.createTable(HBaseOperation.java:39)
    at org.zjenterprise.tizr.hbase.HBaseTestb.main(HBaseTestb.java:33)
Caused by: java.net.SocketTimeoutException: callTimeout=60000, callDuration=71425: row 'mytown:blog,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise06,60020,1434081500945, seqNum=0
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:159)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:310)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:291)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.hadoop.net.ConnectTimeoutException: 10000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.SocketChannel[connection-pending remote=zjenterprise06/60.191.124.236:60020]
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:534)
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupConnection(RpcClientImpl.java:403)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupIOstreams(RpcClientImpl.java:709)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.writeRequest(RpcClientImpl.java:880)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.tracedWriteRequest(RpcClientImpl.java:849)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl.call(RpcClientImpl.java:1173)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:216)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:300)
    at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:31889)
    at org.apache.hadoop.hbase.client.ScannerCallable.openScanner(ScannerCallable.java:344)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:188)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:62)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126)
    ... 6 more
//////////////////////////////////////////////////////////////////////////////////////////////////////////

 

start create table ......
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=36, exceptions:
Mon Jun 01 08:29:21 CST 2015, null, java.net.SocketTimeoutException: callTimeout=60000, callDuration=68287: row 'mytown:myhome,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise05,60021,1432399066976, seqNum=0

    at org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedException(RpcRetryingCallerWithReadReplicas.java:264)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:199)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
    at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:287)
    at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:267)
    at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:139)
    at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:134)
    at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:825)
    at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:601)
    at org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:365)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:291)
    at org.zjenterprise.framework.hbase.HbaseTest.createTable(HbaseTest.java:60)
    at org.zjenterprise.framework.hbase.HbaseTest.main(HbaseTest.java:46)
Caused by: java.net.SocketTimeoutException: callTimeout=60000, callDuration=68287: row 'mytown:myhome,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise05,60021,1432399066976, seqNum=0
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:159)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:294)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:275)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.hadoop.net.ConnectTimeoutException: 10000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.SocketChannel[connection-pending remote=zjenterprise05/60.191.124.236:60021]
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:533)
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:494)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupConnection(RpcClientImpl.java:403)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupIOstreams(RpcClientImpl.java:709)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.writeRequest(RpcClientImpl.java:880)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.tracedWriteRequest(RpcClientImpl.java:849)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl.call(RpcClientImpl.java:1173)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:216)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:300)
    at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:31751)
    at org.apache.hadoop.hbase.client.ScannerCallable.openScanner(ScannerCallable.java:332)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:187)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:62)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126)
    ... 6 more
end create table ......

 

2

---------------------------------------------

 

org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=36, exceptions:
Mon Jun 01 08:42:10 CST 2015, null, java.net.SocketTimeoutException: callTimeout=60000, callDuration=68563: row 'mytown:myhome,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise01,60021,1433119375125, seqNum=0

    at org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedException(RpcRetryingCallerWithReadReplicas.java:264)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:199)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
    at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:287)
    at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:267)
    at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:139)
    at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:134)
    at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:825)
    at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:601)
    at org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:365)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:291)
    at org.zjenterprise.framework.hbase.HbaseTest.createTable(HbaseTest.java:62)
    at org.zjenterprise.framework.hbase.HbaseTest.main(HbaseTest.java:47)
Caused by: java.net.SocketTimeoutException: callTimeout=60000, callDuration=68563: row 'mytown:myhome,,' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=zjenterprise01,60021,1433119375125, seqNum=0
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:159)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:294)
    at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas$RetryingRPC.call(ScannerCallableWithReplicas.java:275)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.hadoop.net.ConnectTimeoutException: 10000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.SocketChannel[connection-pending remote=zjenterprise01/60.191.124.236:60021]
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:533)
    at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:494)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupConnection(RpcClientImpl.java:403)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.setupIOstreams(RpcClientImpl.java:709)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.writeRequest(RpcClientImpl.java:880)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.tracedWriteRequest(RpcClientImpl.java:849)
    at org.apache.hadoop.hbase.ipc.RpcClientImpl.call(RpcClientImpl.java:1173)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:216)
    at org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:300)
    at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:31751)
    at org.apache.hadoop.hbase.client.ScannerCallable.openScanner(ScannerCallable.java:332)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:187)
    at org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:62)
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:126)
    ... 6 more
end create table ......

 

 

 

 

2015-06-11 15:42:13,062 INFO  [main] zookeeper.ZooKeeper: Initiating client connection, connectString=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181 sessionTimeout=120000 watcher=master:600000x0, quorum=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181, baseZNode=/hbase
2015-06-11 15:42:13,072 INFO  [main-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Opening socket connection to server 192.168.3.142/192.168.3.142:2181. Will not attempt to authenticate using SASL (unknown error)
2015-06-11 15:42:13,106 INFO  [main-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Socket connection established to 192.168.3.142/192.168.3.142:2181, initiating session
2015-06-11 15:42:13,122 INFO  [main-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Session establishment complete on server 192.168.3.142/192.168.3.142:2181, sessionid = 0x34de190d9cf0001, negotiated timeout = 40000
2015-06-11 15:42:13,175 INFO  [RpcServer.responder] ipc.RpcServer: RpcServer.responder: starting
2015-06-11 15:42:13,181 INFO  [RpcServer.listener,port=60000] ipc.RpcServer: RpcServer.listener,port=60000: starting
2015-06-11 15:42:13,238 INFO  [main] mortbay.log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
2015-06-11 15:42:13,244 INFO  [main] http.HttpRequestLog: Http request log for http.requests.master is not defined
2015-06-11 15:42:13,251 INFO  [main] http.HttpServer: Added global filter 'safety' (class=org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter)
2015-06-11 15:42:13,255 INFO  [main] http.HttpServer: Added filter static_user_filter (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter) to context master
2015-06-11 15:42:13,255 INFO  [main] http.HttpServer: Added filter static_user_filter (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter) to context logs
2015-06-11 15:42:13,255 INFO  [main] http.HttpServer: Added filter static_user_filter (class=org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter) to context static
2015-06-11 15:42:13,265 INFO  [main] http.HttpServer: Jetty bound to port 16010
2015-06-11 15:42:13,265 INFO  [main] mortbay.log: jetty-6.1.26
2015-06-11 15:42:13,612 INFO  [main] mortbay.log: Started SelectChannelConnector@0.0.0.0:16010
2015-06-11 15:42:13,613 INFO  [main] master.HMaster: hbase.rootdir=hdfs://192.168.3.130:9000/hbase, hbase.cluster.distributed=true
2015-06-11 15:42:13,621 INFO  [main] master.HMaster: Adding backup master ZNode /hbase/backup-masters/zjenterprise01,60000,1434008532400
2015-06-11 15:42:13,734 INFO  [zjenterprise01:60000.activeMasterManager] master.ActiveMasterManager: Deleting ZNode for /hbase/backup-masters/zjenterprise01,60000,1434008532400 from backup master directory
2015-06-11 15:42:13,755 INFO  [zjenterprise01:60000.activeMasterManager] master.ActiveMasterManager: Registered Active Master=zjenterprise01,60000,1434008532400
2015-06-11 15:42:13,772 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.RecoverableZooKeeper: Process identifier=hconnection-0x2bba5623 connecting to ZooKeeper ensemble=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181
2015-06-11 15:42:13,772 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.ZooKeeper: Initiating client connection, connectString=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181 sessionTimeout=120000 watcher=hconnection-0x2bba56230x0, quorum=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181, baseZNode=/hbase
2015-06-11 15:42:13,773 INFO  [master/zjenterprise01/192.168.3.130:60000-SendThread(192.168.3.130:2181)] zookeeper.ClientCnxn: Opening socket connection to server 192.168.3.130/192.168.3.130:2181. Will not attempt to authenticate using SASL (unknown error)
2015-06-11 15:42:13,773 INFO  [master/zjenterprise01/192.168.3.130:60000-SendThread(192.168.3.130:2181)] zookeeper.ClientCnxn: Socket connection established to 192.168.3.130/192.168.3.130:2181, initiating session
2015-06-11 15:42:13,784 INFO  [master/zjenterprise01/192.168.3.130:60000-SendThread(192.168.3.130:2181)] zookeeper.ClientCnxn: Session establishment complete on server 192.168.3.130/192.168.3.130:2181, sessionid = 0x14de190d61e0001, negotiated timeout = 40000
2015-06-11 15:42:13,801 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: ClusterId : a1299f43-a1d1-4189-95cd-963fc5e220b6
2015-06-11 15:42:13,852 INFO  [zjenterprise01:60000.activeMasterManager] util.FSUtils: Waiting for dfs to exit safe mode...
2015-06-11 15:42:24,491 INFO  [zjenterprise01:60000.activeMasterManager] fs.HFileSystem: Added intercepting call to namenode#getBlockLocations so can do block reordering using class class org.apache.hadoop.hbase.fs.HFileSystem$ReorderWALBlocks
2015-06-11 15:42:24,500 INFO  [zjenterprise01:60000.activeMasterManager] coordination.SplitLogManagerCoordination: Found 0 orphan tasks and 0 rescan nodes
2015-06-11 15:42:24,522 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.RecoverableZooKeeper: Process identifier=hconnection-0x4de50506 connecting to ZooKeeper ensemble=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181
2015-06-11 15:42:24,522 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.ZooKeeper: Initiating client connection, connectString=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181 sessionTimeout=120000 watcher=hconnection-0x4de505060x0, quorum=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181, baseZNode=/hbase
2015-06-11 15:42:24,523 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Opening socket connection to server 192.168.3.142/192.168.3.142:2181. Will not attempt to authenticate using SASL (unknown error)
2015-06-11 15:42:24,524 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Socket connection established to 192.168.3.142/192.168.3.142:2181, initiating session
2015-06-11 15:42:24,536 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.142:2181)] zookeeper.ClientCnxn: Session establishment complete on server 192.168.3.142/192.168.3.142:2181, sessionid = 0x34de190d9cf0002, negotiated timeout = 40000
2015-06-11 15:42:24,555 INFO  [zjenterprise01:60000.activeMasterManager] balancer.StochasticLoadBalancer: loading config
2015-06-11 15:42:24,609 INFO  [zjenterprise01:60000.activeMasterManager] master.HMaster: Server active/primary master=zjenterprise01,60000,1434008532400, sessionid=0x34de190d9cf0001, setting cluster-up flag (Was=true)
2015-06-11 15:42:24,629 INFO  [zjenterprise01:60000.activeMasterManager] procedure.ZKProcedureUtil: Clearing all procedure znodes: /hbase/flush-table-proc/acquired /hbase/flush-table-proc/reached /hbase/flush-table-proc/abort
2015-06-11 15:42:24,645 INFO  [zjenterprise01:60000.activeMasterManager] procedure.ZKProcedureUtil: Clearing all procedure znodes: /hbase/online-snapshot/acquired /hbase/online-snapshot/reached /hbase/online-snapshot/abort
2015-06-11 15:42:24,663 INFO  [zjenterprise01:60000.activeMasterManager] master.MasterCoprocessorHost: System coprocessor loading is enabled
2015-06-11 15:42:24,666 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.RecoverableZooKeeper: Process identifier=replicationLogCleaner connecting to ZooKeeper ensemble=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181
2015-06-11 15:42:24,666 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.ZooKeeper: Initiating client connection, connectString=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181 sessionTimeout=120000 watcher=replicationLogCleaner0x0, quorum=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181, baseZNode=/hbase
2015-06-11 15:42:24,667 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.140:2181)] zookeeper.ClientCnxn: Opening socket connection to server 192.168.3.140/192.168.3.140:2181. Will not attempt to authenticate using SASL (unknown error)
2015-06-11 15:42:24,667 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.140:2181)] zookeeper.ClientCnxn: Socket connection established to 192.168.3.140/192.168.3.140:2181, initiating session
2015-06-11 15:42:24,679 INFO  [zjenterprise01:60000.activeMasterManager-SendThread(192.168.3.140:2181)] zookeeper.ClientCnxn: Session establishment complete on server 192.168.3.140/192.168.3.140:2181, sessionid = 0x24de190d5be0006, negotiated timeout = 40000
2015-06-11 15:42:24,698 INFO  [zjenterprise01:60000.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.
2015-06-11 15:42:24,752 INFO  [B.defaultRpcServer.handler=13,queue=1,port=60000] master.ServerManager: Registering server=zjenterprise06,60020,1434008534587
2015-06-11 15:42:24,798 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 1, slept for 100 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2015-06-11 15:42:25,026 INFO  [B.defaultRpcServer.handler=16,queue=1,port=60000] master.ServerManager: Registering server=zjenterprise07,60020,1434008536683
2015-06-11 15:42:25,049 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 2, slept for 351 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2015-06-11 15:42:26,554 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 2, slept for 1856 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2015-06-11 15:42:27,107 INFO  [B.defaultRpcServer.handler=19,queue=1,port=60000] master.ServerManager: Registering server=zjenterprise01,60020,1434008533879
2015-06-11 15:42:27,156 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 3, slept for 2458 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2015-06-11 15:42:28,661 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Waiting for region servers count to settle; currently checked in 3, slept for 3962 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2015-06-11 15:42:29,213 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: Finished waiting for region servers count to settle; checked in 3, slept for 4515 ms, expecting minimum of 1, maximum of 2147483647, master is running
2015-06-11 15:42:29,223 INFO  [zjenterprise01:60000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://192.168.3.130:9000/hbase/WALs/zjenterprise01,60020,1434008533879 belongs to an existing region server
2015-06-11 15:42:29,225 INFO  [zjenterprise01:60000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://192.168.3.130:9000/hbase/WALs/zjenterprise06,60020,1434008534587 belongs to an existing region server
2015-06-11 15:42:29,226 INFO  [zjenterprise01:60000.activeMasterManager] master.MasterFileSystem: Log folder hdfs://192.168.3.130:9000/hbase/WALs/zjenterprise07,60020,1434008536683 belongs to an existing region server
2015-06-11 15:42:29,314 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.MetaTableLocator: Failed verification of hbase:meta,,1 at address=zjenterprise07,60020,1433932864870, exception=org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is not online on zjenterprise07,60020,1434008536683
    at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2749)
    at org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:863)
    at org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegionInfo(RSRpcServices.java:1141)
    at org.apache.hadoop.hbase.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:20862)
    at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2031)
    at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107)
    at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130)
    at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107)
    at java.lang.Thread.run(Thread.java:745)

2015-06-11 15:42:29,319 INFO  [zjenterprise01:60000.activeMasterManager] master.MasterFileSystem: Log dir for server zjenterprise07,60020,1433932864870 does not exist
2015-06-11 15:42:29,319 INFO  [zjenterprise01:60000.activeMasterManager] master.SplitLogManager: dead splitlog workers [zjenterprise07,60020,1433932864870]
2015-06-11 15:42:29,321 INFO  [zjenterprise01:60000.activeMasterManager] master.SplitLogManager: started splitting 0 logs in [] for [zjenterprise07,60020,1433932864870]
2015-06-11 15:42:29,322 INFO  [zjenterprise01:60000.activeMasterManager] master.SplitLogManager: finished splitting (more than or equal to) 0 bytes in 0 log files in [] in 1ms
2015-06-11 15:42:29,323 INFO  [zjenterprise01:60000.activeMasterManager] zookeeper.MetaTableLocator: Deleting hbase:meta region location in ZooKeeper
2015-06-11 15:42:29,375 INFO  [zjenterprise01:60000.activeMasterManager] master.AssignmentManager: Assigning hbase:meta,,1.1588230740 to zjenterprise07,60020,1434008536683
2015-06-11 15:42:29,375 INFO  [zjenterprise01:60000.activeMasterManager] master.RegionStates: Transition {1588230740 state=OFFLINE, ts=1434008549358, server=null} to {1588230740 state=PENDING_OPEN, ts=1434008549375, server=zjenterprise07,60020,1434008536683}
2015-06-11 15:42:29,418 INFO  [zjenterprise01:60000.activeMasterManager] master.ServerManager: AssignmentManager hasn't finished failover cleanup; waiting
2015-06-11 15:42:29,460 INFO  [AM.ZK.Worker-pool2-t1] master.RegionStates: Transition {1588230740 state=PENDING_OPEN, ts=1434008549375, server=zjenterprise07,60020,1434008536683} to {1588230740 state=OPENING, ts=1434008549460, server=zjenterprise07,60020,1434008536683}
2015-06-11 15:42:30,026 INFO  [AM.ZK.Worker-pool2-t2] master.RegionStates: Transition {1588230740 state=OPENING, ts=1434008549460, server=zjenterprise07,60020,1434008536683} to {1588230740 state=OPEN, ts=1434008550025, server=zjenterprise07,60020,1434008536683}
2015-06-11 15:42:30,029 INFO  [AM.ZK.Worker-pool2-t2] coordination.ZkOpenRegionCoordination: Handling OPENED of 1588230740 from zjenterprise01,60000,1434008532400; deleting unassigned node
2015-06-11 15:42:30,041 INFO  [AM.ZK.Worker-pool2-t3] master.RegionStates: Onlined 1588230740 on zjenterprise07,60020,1434008536683
2015-06-11 15:42:30,041 INFO  [zjenterprise01:60000.activeMasterManager] master.HMaster: hbase:meta assigned=1, rit=false, location=zjenterprise07,60020,1434008536683
2015-06-11 15:42:30,108 INFO  [zjenterprise01:60000.activeMasterManager] hbase.MetaMigrationConvertingToPB: hbase:meta doesn't have any entries to update.
2015-06-11 15:42:30,108 INFO  [zjenterprise01:60000.activeMasterManager] hbase.MetaMigrationConvertingToPB: META already up-to date with PB serialization
2015-06-11 15:42:30,149 INFO  [zjenterprise01:60000.activeMasterManager] master.AssignmentManager: Clean cluster startup. Assigning user regions
2015-06-11 15:42:30,172 INFO  [zjenterprise01:60000.activeMasterManager] master.AssignmentManager: Joined the cluster in 64ms, failover=false
2015-06-11 15:42:30,191 INFO  [zjenterprise01:60000.activeMasterManager] master.TableNamespaceManager: Namespace table not found. Creating...
2015-06-11 15:42:30,315 FATAL [zjenterprise01:60000.activeMasterManager] master.HMaster: Failed to become active master
org.apache.hadoop.hbase.TableExistsException: hbase:namespace
    at org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:151)
    at org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:124)
    at org.apache.hadoop.hbase.master.TableNamespaceManager.createNamespaceTable(TableNamespaceManager.java:233)
    at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:86)
    at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:871)
    at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:722)
    at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:165)
    at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1428)
    at java.lang.Thread.run(Thread.java:745)
2015-06-11 15:42:30,318 FATAL [zjenterprise01:60000.activeMasterManager] master.HMaster: Master server abort: loaded coprocessors are: []
2015-06-11 15:42:30,318 FATAL [zjenterprise01:60000.activeMasterManager] master.HMaster: Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.TableExistsException: hbase:namespace
    at org.apache.hadoop.hbase.master.handler.CreateTableHandler.checkAndSetEnablingTable(CreateTableHandler.java:151)
    at org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:124)
    at org.apache.hadoop.hbase.master.TableNamespaceManager.createNamespaceTable(TableNamespaceManager.java:233)
    at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:86)
    at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:871)
    at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:722)
    at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:165)
    at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1428)
    at java.lang.Thread.run(Thread.java:745)
2015-06-11 15:42:30,318 INFO  [zjenterprise01:60000.activeMasterManager] regionserver.HRegionServer: STOPPED: Unhandled exception. Starting shutdown.
2015-06-11 15:42:30,318 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: Stopping infoServer
2015-06-11 15:42:30,321 INFO  [master/zjenterprise01/192.168.3.130:60000] mortbay.log: Stopped SelectChannelConnector@0.0.0.0:16010
2015-06-11 15:42:30,422 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: stopping server zjenterprise01,60000,1434008532400
2015-06-11 15:42:30,429 INFO  [master/zjenterprise01/192.168.3.130:60000] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x14de190d61e0001
2015-06-11 15:42:30,447 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.ZooKeeper: Session: 0x14de190d61e0001 closed
2015-06-11 15:42:30,447 INFO  [master/zjenterprise01/192.168.3.130:60000-EventThread] zookeeper.ClientCnxn: EventThread shut down
2015-06-11 15:42:30,502 INFO  [zjenterprise01,60000,1434008532400.splitLogManagerTimeoutMonitor] master.SplitLogManager$TimeoutMonitor: zjenterprise01,60000,1434008532400.splitLogManagerTimeoutMonitor exiting
2015-06-11 15:42:30,548 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: stopping server zjenterprise01,60000,1434008532400; all regions closed.
2015-06-11 15:42:30,549 INFO  [zjenterprise01,60000,1434008532400-BalancerChore] balancer.BalancerChore: zjenterprise01,60000,1434008532400-BalancerChore exiting
2015-06-11 15:42:30,549 INFO  [zjenterprise01:60000.oldLogCleaner] cleaner.LogCleaner: zjenterprise01:60000.oldLogCleaner exiting
2015-06-11 15:42:30,549 INFO  [CatalogJanitor-zjenterprise01:60000] master.CatalogJanitor: CatalogJanitor-zjenterprise01:60000 exiting
2015-06-11 15:42:30,549 INFO  [zjenterprise01,60000,1434008532400-ClusterStatusChore] balancer.ClusterStatusChore: zjenterprise01,60000,1434008532400-ClusterStatusChore exiting
2015-06-11 15:42:30,549 INFO  [zjenterprise01:60000.oldLogCleaner] master.ReplicationLogCleaner: Stopping replicationLogCleaner-0x24de190d5be0006, quorum=192.168.3.140:2181,192.168.3.130:2181,192.168.3.142:2181, baseZNode=/hbase
2015-06-11 15:42:30,550 INFO  [zjenterprise01:60000.archivedHFileCleaner] cleaner.HFileCleaner: zjenterprise01:60000.archivedHFileCleaner exiting
2015-06-11 15:42:30,557 INFO  [zjenterprise01:60000.oldLogCleaner] zookeeper.ZooKeeper: Session: 0x24de190d5be0006 closed
2015-06-11 15:42:30,557 INFO  [zjenterprise01:60000.activeMasterManager-EventThread] zookeeper.ClientCnxn: EventThread shut down
2015-06-11 15:42:30,565 INFO  [master/zjenterprise01/192.168.3.130:60000] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x34de190d9cf0002
2015-06-11 15:42:30,606 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.ZooKeeper: Session: 0x34de190d9cf0002 closed
2015-06-11 15:42:30,606 INFO  [zjenterprise01:60000.activeMasterManager-EventThread] zookeeper.ClientCnxn: EventThread shut down
2015-06-11 15:42:30,707 INFO  [master/zjenterprise01/192.168.3.130:60000] flush.MasterFlushTableProcedureManager: stop: server shutting down.
2015-06-11 15:42:30,708 INFO  [master/zjenterprise01/192.168.3.130:60000] ipc.RpcServer: Stopping server on 60000
2015-06-11 15:42:30,708 INFO  [RpcServer.listener,port=60000] ipc.RpcServer: RpcServer.listener,port=60000: stopping
2015-06-11 15:42:30,709 INFO  [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopped
2015-06-11 15:42:30,709 INFO  [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopping
2015-06-11 15:42:30,731 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.RecoverableZooKeeper: Node /hbase/rs/zjenterprise01,60000,1434008532400 already deleted, retry=false
2015-06-11 15:42:30,739 INFO  [master/zjenterprise01/192.168.3.130:60000] zookeeper.ZooKeeper: Session: 0x34de190d9cf0001 closed
2015-06-11 15:42:30,739 INFO  [main-EventThread] zookeeper.ClientCnxn: EventThread shut down
2015-06-11 15:42:30,739 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: stopping server zjenterprise01,60000,1434008532400; zookeeper connection closed.
2015-06-11 15:42:30,745 INFO  [master/zjenterprise01/192.168.3.130:60000] regionserver.HRegionServer: master/zjenterprise01/192.168.3.130:60000 exiting

分享到:
评论
2 楼 Gamehu520 2017-06-29  
table中无数据
1 楼 Xleer0102 2016-10-08  
为什么都是只有问没有答,哭晕在厕所

相关推荐

    HbaseTemplate 操作hbase

    8. **异常处理**:在使用HbaseTemplate时,需要注意处理可能出现的异常,如TableExistsException(表已存在)、TableNotFoundException(表不存在)等,确保程序的健壮性。 总之,Spring Data Hadoop的Hbase...

    16:Flume+HBase+Kafka集成开发.rar

    Kafka作为一个高可用的消息中间件,可以缓冲数据,确保即使在Flume或HBase出现问题时,数据也不会丢失。同时,多个Flume实例可以并发地将数据推送到同一个Kafka Topic,提供高并发的数据摄入能力。 然后,Kafka的...

    hbase安装,节点添加,移除,常见问题解决

    3. **HDFS问题**:如果HDFS出现问题,如NameNode故障,需要解决Hadoop的问题后再恢复HBase。 4. **Region分裂**:过多的数据可能导致Region过大,需要手动或自动分裂Region以保持均衡。 5. **延迟问题**:监控系统...

    hbase安装与使用

    如果出现错误提示,例如 Master 启动失败的情况,可以通过检查日志文件找到具体的错误信息。例如: ```bash 2015-02-02 03:25:33,639 ERROR [main] master.HMasterCommandLine: Master exiting java.lang....

    hive和hbase整合

    解决这个问题可能需要检查以下几个方面: - 确保ZooKeeper服务正在运行。 - 检查Hive与HBase的配置文件中ZooKeeper的地址是否正确。 - 检查网络连接是否畅通,确保Hive和HBase可以访问到ZooKeeper服务器。 - 如果...

    hbase社区2018精选资料

    HBCK2是一个修复工具,用于解决HBase中可能出现的数据一致性问题。 HBase社区的平台建设也是资料的一个重点,文档提到通过平台实践和应用,可以更好地构建和管理大数据系统。这不仅包括硬件层面的存储介质选择,也...

    Hbase实验报告.pdf

    如果出现错误,应检查Hadoop和HBase的配置文件,如`hbase-site.xml`和`hbase-env.sh`,确保它们指向正确的路径和服务端口。 通过这个实验,我们不仅掌握了HBase的基本操作,还理解了NoSQL数据库在大数据处理中的...

    在Ubuntu安装配置hbase

    在Ubuntu系统上安装配置HBase是一项重要的任务,尤其对于那些需要处理大规模数据的项目而言。HBase是一个分布式的、面向列的开源...同时,理解HBase的数据模型和工作原理对于优化配置和解决可能出现的问题至关重要。

    python3连接hbase包

    因此,这个包的出现解决了 Python3 用户在连接 HBase 时遇到的困扰。 首先,我们需要了解如何在 Python3 中安装这个连接 HBase 的库。通常,你可以使用 pip(Python 的包管理器)来安装,命令可能是 `pip install ...

    HBase2.x之RIT问题解决.docx

    在RIT过程中,可能会出现异常情况,从而导致Region的状态一直保持在RIT,使得HBase出现异常。 解决RIT问题需要从多方面入手,下面是四种解决方案: 方案一:检查HDFS的健康度 首先,需要检查HDFS的健康度,是否有...

    hbase的rowkey设计与hbase的协处理器运用.docx

    5. 高可靠性:WAL 机制保证了数据写入时不会因集群异常而导致写入数据丢失,Replication 机制保证了在集群出现严重的问题时,数据不会发生丢失或损坏。 6. 高性能:底层的 LSM 数据结构和 Rowkey 有序排列等架构上的...

    hbase常见错误整理3年运维经验整理

    ### HBase常见错误及解决方案:3年运维经验总结 #### 一、配置第三方依赖包HADOOP_CLASSPATH和HBase问题 **问题描述** ...通过以上措施,可以有效缓解高并发写入场景下HBase与HDFS交互时出现的超时问题。

    HBase负载均衡分析及优化策略

    针对原有负载均衡算法在负载分配过程中可能产生的负载严重不均衡问题,通过分析原有算法和问题出现的因素,提出一种基于子表限制的负载均衡改进方法,并通过与不均衡状况下的对比实验,验证改进后的分配方式可以有效利用...

    HBase Introduction

    - **避免热点**:由于数据是以有序的方式存储的,因此避免使用顺序的行键写入数据可以防止出现热点问题。 - **预分割**:在创建表时进行预分割是一种常见的优化方法。从单个区域开始意味着最初所有数据都由一个...

    hbase

    当区域服务器出现故障时,HMaster会进行故障恢复,重新分配该服务器上的区域。 2. **区域服务器(RegionServer)**:每个区域服务器负责管理多个HBase表的区域,区域是HBase存储数据的基本单元。区域服务器执行所有...

    C#操控hbase数据库

    9. **异常处理**:在C#中,正确处理HBase操作可能出现的异常,确保程序的健壮性。 10. **安全性**:如果是在生产环境中,还需要考虑数据的安全性,包括认证、授权和加密。 压缩包中的"MyHbase"可能是包含这些功能...

    Hadoop Hive与Hbase整合

    另外,需要注意的是,在整合Hive和Hbase时,需要注意配置文件的正确性和一致性,否则可能会出现各种错误和问题。例如,如果hive-site.xml文件中的配置信息不正确,可能会导致Hive无法连接到Hbase数据库。同时,如果...

    HBase in Practise: 性能、监控和问题排查

    在生产环境可能出现各种问题,而监控系统是发现并解决问题的关键。目前HBase提供了大量的metrics用于监控,其中有哪些是要特别关注的?线上不同类型的问题应该重点查看哪些metrics来定位问题?如何结合metrics和...

    HBase性能深度分析

    ### HBase性能深度分析 HBase,作为BigTable的一个开源实现,因其卓越的分布式数据库特性在大数据处理领域占据了重要地位。然而,随着HBase在各行业的广泛应用,用户对其性能表现的关注日益增强,尤其是实时数据...

Global site tag (gtag.js) - Google Analytics