Shulou(Shulou.com)06/01 Report--

Hbase failed to empower the user and reported an error.

Background description of the problem:

Test environment, hdfs has been format. Many hdfs-based environments have been affected. Hbase has also been affected. But in the process of starting hbase in master, as long as there is a / hbase directory on hdfs

After building the table, we found that there were errors in the process of empowerment.

Hbase (main): 001Security features are not availablehbase 0 > user_permissionUser Namespace,Table,Family,Qualifier:PermissionERROR: DISABLED: Security features are not availablehbase (main): 001user_permissionUser Namespace,Table,Family,Qualifier:PermissionERROR 0 > grant 'test_user',' RWXCA', 'test_table'ERROR: DISABLED: Security features are not availableHere is some help for this command:Grant users specific rights.Syntax: grant, [,]] hbase (main): 002user_permissionUser Namespace,Table,Family,Qualifier:PermissionERROR 0 > hbase:aclNoMethodError: undefined method `hbase' for #

two。 At first I thought there was something wrong with the grammar. No, it's a very simple grammar. After testing several commands, it is found that all commands related to permissions have failed.

Baidu has some suggestions and needs to check the parameters. After confirming that the following parameters are set correctly, the problem remains.

Hbase.master.keytab.filehbase.master.kerberos.principalhbase.regionserver.keytab.filehbase.regionserver.kerberos.principalhbase.coprocessor.master.classeshbase.coprocessor.region.classeshbase.security.authorization

3. Baidu goes to the following link, which has an introduction:

Reference link

Https://community.hortonworks.com/questions/50984/security-features-not-available-in-hbase-kerberize.htmlIt seems your hbase:acl table is not created.can you check hbase-site.xml at master side as well it should have:- hbase.coprocessor.master.classes org.apache.hadoop.hbase.security.access.AccessController try restarting your cluster as postStartMaster step should create this table, once you are able to do scan 'hbase:acl', you will not see above error "ERROR: DISABLED:Security features are not available"

4. The following sentence reminds me that hbase:acl is missing.

Try restarting your cluster as postStartMaster step should create this table, once you are able to do scan 'hbase:acl'

5. Upon inspection, it was found that it was really gone.

6. The normal situation should be

7. The cause of the problem has been found. Let's start looking for a solution. Continue Baidu (search technical documentation, especially miss google)

How to rebuild hbase:acl? Hbase does not have any special settings during installation, as long as you create a / hbase directory on hdfs, starting hbase master will automatically create the required files. Why didn't you recreate the acl table after several restarts?

Looking at hbase master log, you can see the error "The table hbase:acl does not exist in meta but has a znode. Run hbck to fix inconsistencies." Checked by the command hbase hbck, there are no errors. The problem has not been solved.

2018-02-24 16 INFO 41master.HMaster [testserver:16000.activeMasterManager] master.HMaster: Master has completed initialization2018-02-24 16V 41V 40016 INFO [testserver:16000.activeMasterManager] quotas.MasterQuotaManager: Quota support disabled2018-02-24 16V 41V 40062 INFO [testserver:16000.activeMasterManager] master.HMaster: Client=null/null create 'hbase:acl', {NAME = >' 1mm, DATA_BLOCK_ENCODING = > 'NONE', BLOOMFILTER = >' NONE', REPLICATION_SCOPE = > '01', COMPRESSION = >' NONE', VERSIONS = >'1' TTL = > 'FOREVER', MIN_VERSIONS = >' 019', CACHE_DATA_IN_L1 = > 'true', KEEP_DELETED_CELLS = >' FALSE', BLOCKSIZE = > '8192', IN_MEMORY = > 'true', BLOCKCACHE = >' true'} 2018-02-24 16 purse 41 1 CACHE_DATA_IN_L1 40200 WARN [ProcedureExecutorThread-1] procedure.CreateTableProcedure: The table hbase:acl does not exist in meta but has a znode. Run hbck to fix inconsistencies.2018-02-24 16 testserver:16000.activeMasterManager 41V 40202 ERROR [testserver:16000.activeMasterManager] master.HMaster: Coprocessor postStartMaster () hook failedorg.apache.hadoop.hbase.TableExistsException: hbase:aclat org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate (CreateTableProcedure.java:300) at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState (CreateTableProcedure.java:107) at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState (CreateTableProcedure.java:58) at org.apache.hadoop Execute (StateMachineProcedure.java:107) at org.apache.hadoop.hbase.procedure2.Procedure.doExecute (Procedure.java:427) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure (ProcedureExecutor.java:999) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop (ProcedureExecutor.java:803) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop (ProcedureExecutor.java:756) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$200 (ProcedureExecutor.java:75) At org.apache.hadoop.hbase.procedure2.ProcedureExecutor$1.run (ProcedureExecutor.java:441) 2018-02-24 16 INFO 41V 40496 INFO [ProcedureExecutorThread-1] procedure2.ProcedureExecutor: Rolledback procedure CreateTableProcedure (table=hbase:acl) id=2 owner=hbase state=ROLLEDBACK exec-time=299msec exception=org.apache.hadoop.hbase.TableExistsException: hbase:acl2018-02-24 16V 46Zhou 05790 INFO [LruBlockCacheStatsExecutor] hfile.LruBlockCache: totalSize=3.24 MB FreeSize=3.08 GB, max=3.08 GB, blockCount=0, accesses=0, hits=0, hitRatio=0, cachingAccesses=0, cachingHits=0, cachingHitsRatio=0,evictions=29, evicted=0, evictedPerRun=0.0

8. The error is reported above, now that the problem with znode has been clearly mentioned, let's check the situation on zookeeper.

Indeed, we can see that the information that failed when preparing for empowerment was recorded under the acl path of znode.

Hbase zkcli [zk: 192.168.0.72 ls 2181 (CONNECTED) 3] ls / hbase [meta-region-server, acl, backup-masters, table, draining, region-in-transition, running, table-lock, balancer, master, tokenauth, namespace, hbaseid, online-snapshot, replication, splitWAL, recovering-regions, rs Flush-table-proc] [zk: 192.168.0.72 CONNECTED 2181192.168.0.73 CONNECTED] ls / hbase/acl [@ test_user]

9. Delete the / hbase information on zk, then restart the entire hbase cluster and let hbase automatically rebuild the acl table

[zk: 192.168.0.72 rmr 2181 (CONNECTED) 6] rmr / hbase [zk: 192.168.0.72 rmr 2181 (CONNECTED) 7] ls / [alert, kafka-manager-1.3.3.13, rmstore, yarn-leader-election, kafka10-dev2, livy, kafka10, kafka10-dev, dubbo, eos, alert_leader, election, DP, hadoop-ha, zookeeper, leader User] [zk: 192.168.0.72 hbase@testserver 2181192.168.0.73 CONNECTED 2181 (CONNECTED) 8] [hbase@testserver ~] $exit

10. As you can see, the file has come back.

[hdfs@testserver] $hdfs dfs-ls / hbase/data/hbaseFound 3 itemsdrwxrwx----hbase hadoop 0 2018-02-24 17:00 / hbase/data/hbase/acldrwxrwx----hbase hadoop 0 2018-02-24 16:59 / hbase/data/hbase/metadrwxrwx----hbase hadoop 0 2018-02-24 17:00 / hbase/data/hbase/namespace

The 11.acl table can also be viewed.

Hbase (main): 004hbase:acl'ROW COLUMN+CELLtest_table column=l:hbase 0 > scan 'hbase:acl'ROW COLUMN+CELLtest_table column=l:hbase, timestamp=1519463374193, value=RWXCAtest_table_01 column=l:hbase, timestamp=1519463409831, value=RWXCAuser_01 column=l:hbase, timestamp=1519463393177 Value=RWXCA3 row (s) in 0.1600 seconds

Problems encountered, in the case of understanding the principle of the overall architecture, purposeful, scope of step-by-step inspection, can eventually be solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.