【问题标题】:ERROR: hbase:meta table is not consistent错误:hbase:meta 表不一致
【发布时间】:2018-10-06 04:56:34
【问题描述】:

在 HBASE 中创建表时出错。 “错误:java.io.IOException:表命名空间管理器尚未准备好,请尝试 稍后再来。”

hcbk -fix 显示 ERROR: hbase:meta is not found on any region.

在重新启动 hbase shell 会话后出现错误启动期间主日志中没有报告错误。 上次 Hbase 会话正常关闭,但 zookeeper 未正常关闭(怀疑这是元表损坏的原因)。

我可以列出之前创建的表

hbase(main):001:0> list
TABLE
IDX_STOCK_SYMBOL
Patient
STOCK_SYMBOL
STOCK_SYMBOL_BKP
SYSTEM.CATALOG
SYSTEM.FUNCTION
SYSTEM.SEQUENCE
SYSTEM.STATS
8 row(s) in 1.7930 seconds

创建一个名为 custmaster 的表

    hbase(main):002:0> create 'custmaster', 'customer'

    ERROR: java.io.IOException: Table Namespace Manager not ready yet, try 
    again later
    at org.apache.hadoop.hbase.master.HMaster.getNamespaceDescriptor(HMaster.java:3179)
    at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1735)
    at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1774)
    at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:40470)
    at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
    at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)
    at org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:74)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

解决方法:运行 hbck 以识别不一致

    [hduser@master ~]$ hbase hbck
    >Version: 0.98.4-hadoop2
    >Number of live region servers: 2
    >Number of dead region servers: 0
    >Master: master,60000,1538793456542
    >Number of backup masters: 0
    >Average load: 0.0
    >Number of requests: 11
    >Number of regions: 0
    >Number of regions in transition: 1
    >
    >ERROR: META region or some of its attributes are null.
    >ERROR: hbase:meta is not found on any region.
    >ERROR: hbase:meta table is not consistent. Run HBCK with proper fix options to fix hbase:meta inconsistency. Exiting...
    .
    .
    .
    >Summary:                >
    >3 inconsistencies detected.
    >Status: INCONSISTENT

运行 hbck wih-details 选项以识别所涉及的表

    [hduser@master ~]$ hbase hbck -details
    >ERROR: META region or some of its attributes are null.
    >ERROR: hbase:meta is not found on any region.
    >ERROR: hbase:meta table is not consistent. Run HBCK with proper fix options to fix hbase:meta inconsistency. Exiting...
    >Summary:
    >3 inconsistencies detected.
    >Status: INCONSISTENT

-details 的输出清楚地表明在任何区域都找不到元数据。

尝试运行命令 hbase hbck -fixMeta 但返回的结果与上面相同 因此尝试了 hbase hbck -fix

此命令运行了一段时间,提示 “尝试修复 hbase:meta.. 的问题” 并导致以下错误

    [hduser@master ~]$ hbase hbck -fix

    Version: 0.98.4-hadoop2
    Number of live region servers: 2
    Number of dead region servers: 0
    Master: master,60000,1538793456542
    Number of backup masters: 0
    Average load: 0.0
    Number of requests: 19
    Number of regions: 0
    Number of regions in transition: 1
    ERROR: META region or some of its attributes are null.
    ERROR: hbase:meta is not found on any region.
    Trying to fix a problem with hbase:meta..
    2018-10-06 09:01:03,424 INFO  [main] client.HConnectionManager$HConnectionImplementation: Closing master protocol: MasterService
    2018-10-06 09:01:03,425 INFO  [main] client.HConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x166473bbe720005
    2018-10-06 09:01:03,432 INFO  [main] zookeeper.ZooKeeper: Session: 0x166473bbe720005 closed
    2018-10-06 09:01:03,432 INFO  [main-EventThread] zookeeper.ClientCnxn: EventThread shut down
    Exception in thread "main" org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:
    Sat Oct 06 08:52:13 IST 2018, org.apache.hadoop.hbase.client.RpcRetryingCaller@18920cc, org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.PleaseHoldException): org.apache.hadoop.hbase.PleaseHoldException: Master is initializing
            at org.apache.hadoop.hbase.master.HMaster.checkInitialized(HMaster.java:2416)
            at org.apache.hadoop.hbase.master.HMaster.assignRegion(HMaster.java:2472)
            at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:40456)
            at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
            at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)
            at org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:74)
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
            at java.util.concurrent.FutureTask.run(FutureTask.java:266)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at java.lang.Thread.run(Thread.java:748)

    Sat Oct 06 08:52:13 IST 2018, org.apache.hadoop.hbase.client.RpcRetryingCaller@18920cc, org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.PleaseHoldException): org.apache.hadoop.hbase.PleaseHoldException: Master is initializing
            at org.apache.hadoop.hbase.master.HMaster.checkInitialized(HMaster.java:2416)
            at org.apache.hadoop.hbase.master.HMaster.assignRegion(HMaster.java:2472)
            at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:40456)
            at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
            at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)
            at org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:74)
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
            at java.util.concurrent.FutureTask.run(FutureTask.java:266)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at java.lang.Thread.run(Thread.java:748)

请帮我解决这个问题? 提前致谢!!

【问题讨论】:

    标签: hadoop hbase


    【解决方案1】:

    我还没有检查过 NameNode 和 Datanode 日志。但是当我检查真正的问题时发现是 HDFS 中的文件损坏。

    运行 hadoop fsck / 来检查文件系统的健康状况。

        [hduser@master ~]$ hadoop fsck /
        DEPRECATED: Use of this script to execute hdfs command is deprecated.
        Instead use the hdfs command for it.
    
        18/10/06 09:52:00 WARN util.NativeCodeLoader: Unable to load native-hadoop libr
        ary for your platform... using builtin-java classes where applicable
        Connecting to namenode via http://master:50070/fsck?ugi=hduser&path=%2F
        FSCK started by hduser (auth:SIMPLE) from /192.168.1.11 for path / at Sat Oct 0
        6 09:52:02 IST 2018
        ...............................................................................
        ..
        /user/hduser/hbase/.hbck/hbase-1538798774320/data/hbase/meta/1588230740/info/35
        9783d4cd07419598264506bac92dcf: CORRUPT blockpool BP-1664228054-192.168.1.11-15
        35828595216 block blk_1073744002
    
        /user/hduser/hbase/.hbck/hbase-1538798774320/data/hbase/meta/1588230740/info/35                                                   9783d4cd07419598264506bac92dcf: MISSING 1 blocks of total size 3934 B.........
        /user/hduser/hbase/data/default/IDX_STOCK_SYMBOL/a27db76f84487a05f3e1b8b74c13fa
        78/0/c595bf49443f4daf952df6cdaad79181: CORRUPT blockpool BP-1664228054-192.168.
        1.11-1535828595216 block blk_1073744000
    
        /user/hduser/hbase/data/default/IDX_STOCK_SYMBOL/a27db76f84487a05f3e1b8b74c13fa
        78/0/c595bf49443f4daf952df6cdaad79181: MISSING 1 blocks of total size 1354 B...
        .........
        ...
        /user/hduser/hbase/data/default/SYSTEM.CATALOG/d63574fdd00e8bf3882fcb6bd53c3d83
        /0/dcb68bbb5e394d19b06db7f298810de0: CORRUPT blockpool BP-1664228054-192.168.1.
        11-1535828595216 block blk_1073744001
    
        /user/hduser/hbase/data/default/SYSTEM.CATALOG/d63574fdd00e8bf3882fcb6bd53c3d83
        /0/dcb68bbb5e394d19b06db7f298810de0: MISSING 1 blocks of total size 2283 B.....                                                   ......................Status: CORRUPT
         Total size:    4232998 B
         Total dirs:    109
         Total files:   129
         Total symlinks:                0
         Total blocks (validated):      125 (avg. block size 33863 B)
          ********************************
          UNDER MIN REPL'D BLOCKS:      3 (2.4 %)
          dfs.namenode.replication.min: 1
          CORRUPT FILES:        3
          MISSING BLOCKS:       3
          MISSING SIZE:         7571 B
          CORRUPT BLOCKS:       3
          ********************************
         Minimally replicated blocks:   122 (97.6 %)
         Over-replicated blocks:        0 (0.0 %)
         Under-replicated blocks:       0 (0.0 %)
         Mis-replicated blocks:         0 (0.0 %)
         Default replication factor:    2
         Average block replication:     1.952
         Corrupt blocks:                3
         Missing replicas:              0 (0.0 %)
         Number of data-nodes:          2
         Number of racks:               1
        FSCK ended at Sat Oct 06 09:52:02 IST 2018 in 66 milliseconds
    
    
        The filesystem under path '/' is CORRUPT
    

    然后我运行 hdfs hbck -delete 选项来删除损坏的文件并修复问题。

    这里有关于清理hdfs f/s的详细解释 --> How to fix corrupt HDFS FIles

    【讨论】:

      猜你喜欢
      • 2015-07-25
      • 1970-01-01
      • 2020-06-27
      • 2010-11-26
      • 2018-05-27
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2016-09-12
      相关资源
      最近更新 更多