Member since
09-28-2018
21
Posts
1
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2362 | 10-06-2018 01:46 PM | |
7257 | 10-04-2018 03:09 AM |
09-24-2019
10:55 PM
Hi @linuslukia or anyone else... can you PLEASE tell us what is the solution for this problem? I tried and last advice with deleteing the WALS and rm from /hbase-unsecure/rs and restarted zookeeper and hbase and it didn't work.
... View more
10-21-2018
03:34 AM
Thanky you, this resolved an issue
... View more
10-18-2018
04:15 AM
@bgooley just to add that I have following folders (if the issue is related to folders on HDFS) [cloudera-scm@cv-nn2 ~]$ hdfs dfs -ls /user Found 3 items drwxr-xr-x - cloudera-scm supergroup 0 2018-10-09 08:53 /user/cloudera-scm drwxrwx--- - cloudera-scm supergroup 0 2018-10-05 06:56 /user/history drwxrwxr-x - hue hue 0 2018-10-05 06:57 /user/hue
... View more
10-18-2018
04:00 AM
@bgooley thank you for reply. This is the output from my analysis. /var/log/cloudera-scm-firehose/mgmt-cmf-mgmt-SERVICEMONITOR 2018-10-18 10:48:15,050 WARN com.cloudera.cmf.cdh5client.hive.MetastoreClientImpl: Could not create a hive database cloudera_manager_metastore_canary_test_db_hive_HIVEMETASTORE_ba135b5c35747b251098753b881a186b MetaException(message:Got exception: org.apache.hadoop.security.AccessControlException Permission denied: user=hue, access=EXECUTE, inode="/user":cloudera-scm:supergroup:drwxrwx--- at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.checkFsPermission(DefaultAuthorizationProvider.java:279) at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.check(DefaultAuthorizationProvider.java:260) at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.checkTraverse(DefaultAuthorizationProvider.java:201) at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.checkPermission(DefaultAuthorizationProvider.java:154) 2018-10-18 10:48:15,051 WARN com.cloudera.cmon.firehose.polling.hive.HiveMetastoreCanary: Metastore hive-HIVEMETASTORE-ba135b5c35747b251098753b881a186b:Failed to create database com.cloudera.cmf.cdhclient.common.hive.MetaException: Got exception: org.apache.hadoop.security.AccessControlException Permission denied: user=hue, access=EXECUTE, inode="/user":cloudera-scm:supergroup:drwxrwx--- I am not sure for what this permission is denied? Can you please assist what should be corrected and how? /var/log/hive/hadoop-cmf-HIVE-1-HIVEMETASTORE 2018-10-18 10:53:32,573 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [pool-5-thread-3]: 3: source:10.0.9.4 create_database: Database(name:cloudera_manager_metastore_canary_test_db_hive_HIVEMETASTORE_ba135b5c35747b251098753b881a186b, description:Cloudera Manager Metastore Canary Test Database, locationUri:/user/hue/.cloudera_manager_hive_metastore_canary/hive_HIVEMETASTORE_ba135b5c35747b251098753b881a186b, parameters:null) 2018-10-18 10:53:32,573 INFO org.apache.hadoop.hive.metastore.HiveMetaStore.audit: [pool-5-thread-3]: ugi=hue ip=10.0.9.4 cmd=source:10.0.9.4 create_database: Database(name:cloudera_manager_metastore_canary_test_db_hive_HIVEMETASTORE_ba135b5c35747b251098753b881a186b, description:Cloudera Manager Metastore Canary Test Database, locationUri:/user/hue/.cloudera_manager_hive_metastore_canary/hive_HIVEMETASTORE_ba135b5c35747b251098753b881a186b, parameters:null) 2018-10-18 10:53:32,694 ERROR hive.log: [pool-5-thread-3]: Got exception: org.apache.hadoop.security.AccessControlException Permission denied: user=hue, access=EXECUTE, inode="/user":cloudera-scm:supergroup:drwxrwx--- I think that maybe there is some issue with folder? But not sure exactly with what folder? Thank you
... View more
10-17-2018
12:29 AM
Can someone please provide me steps how to resolve this or what should be the following debugging steps? Thank you
... View more
10-11-2018
05:33 AM
Hive is being run on Name Node 1. When I start Hive service everything is green and up and running: Hive Metastore Server HiveServer2 WebHCat Server After few minutes Hive Metastore Server becomes unavailable with bad health: Hive Metastore Canary "The Hive Metastore canary failed to create a database." Few more information: we do not have any MySQL database, we are using OOTB configuration for Hive, so it is probably Postgre I already run command Update Hive Metastore Database Schema and Update Hive Metastore Name Nodes after installation. They are grey now. Please advise for further steps. Thank you
... View more
Labels:
- Labels:
-
Apache Hive
-
Cloudera Manager
10-06-2018
01:46 PM
Hi, solution is that in /var/hdfs-sockets/dn dn should not be created as directory. dn will be created automatically as a file. My mistake was becase I created dn also as directory and that is why I was getting an error. Thank you for assitance
... View more
10-04-2018
03:09 AM
This is resolved. Solution was that last segment is the file and will be created automatically. It should not be created as dir.
... View more
10-04-2018
01:54 AM
Hi @manuroman can you please provide more details? 1. for chaging the port - were you reffering to Data Node port 50010 or some other port? Also I am confused here because UNIX domain socket is networkless, which should imply that ports are not relevant? Please tell me on which exact port you were reffering to? 2. for killing the PID can you please tell me on which exact process you were reffering that should be killed in order to start HDFS? Are you reffering to some process on DataNode or...? Thank you in advance, Veljko
... View more
10-04-2018
01:34 AM
Hi, I am facing the same issue. I tried with both users: root and cloudera-scm to set as owners for /var/hdfs-sockets/dn. Error is: Address already in use when trying to bind to '/var/hdfs-sockets/dn' But without success. Can someone please provide some hints on this? Thanks
... View more
Labels:
- Labels:
-
HDFS