Member since
04-10-2019
33
Posts
0
Kudos Received
0
Solutions
06-15-2019
08:04 AM
Hi @Jay Kumar SenSharma. I just checked my FQDN and they are all correct : master.rh.bigdata.cluster node2.rh.bigdata.cluster node3.rh.bigdata.cluster node4.rh.bigdata.cluster Still got the error !
... View more
06-11-2019
10:52 AM
@Adil BAKKOURI We see the following message seems to be causing the DataNode startup failure. 2019-06-11 12:30:52,832 WARN common.Storage (DataStorage.java:loadDataStorage(418)) - Failed to add storage directory [DISK]file:/hadoop/hdfs/data
java.io.IOException: Incompatible clusterIDs in /hadoop/hdfs/data: namenode clusterID = CID-bd1a4e24-9ff2-4ab8-928a-f04000e375cc; datanode clusterID = CID-9a605cbd-1b0e-41d3-885e-f0efcbe54851 Looks like your VERSION file has different cluster IDs present in NameNode and DataNode that need to be correct. Please copy the clusterID from nematode "<dfs.namenode.name.dir>/current/VERSION" and put it in the VERSION file of datanode "<dfs.datanode.data.dir>/current/VERSION" and then try again. Also please check the following link: https://community.hortonworks.com/questions/79432/datanode-goes-dows-after-few-secs-of-starting-1.html
... View more
06-11-2019
10:21 AM
@Adil BAKKOURI Based on your Latest Logs it looks like after changing the permissions the NameNode is starting fine without any issue. For the DataNode not starting issue please open a Separate HCC thread and Mark this HCC thread as Answered by clicking on "Accept" link on correct answer.
... View more
05-10-2019
10:01 PM
@Adil BAKKOURI Hurrah we are now there, thats the error I was expecting now this is a case closed. Validate the hostname by running # hostname -f This should give you the FQDN The error below is very simple its a privilege issue with the hive user and database creation script you run, you didn't give the correct privileges to the hive user "Access denied for user 'hive'@'master.rh.bigdata.cluster' to database 'hive'" To resolve the above please do the following assumptions Root password = gr3atman Hive password = hive Hostname = master.rh.bigdata.cluster mysql -uroot -pgr3atman
mysql> GRANT ALL PRIVILEGES ON hive.* to 'hive'@'localhost' identified by 'hive';
mysql> GRANT ALL PRIVILEGES ON hive.* to 'hive'@'master.rh.bigdata.cluster' identified by 'hive';
mysql> GRANT ALL PRIVILEGES ON hive.* TO 'hive'@'master.rh.bigdata.cluster';
mysql> flush privileges; All of the above should succeed. Now your hive should fire up Bravo !! ************ If you found this answer addressed your question, please take a moment to log in and click the "accept" link on the answer. That would be a great help to Community users to find the solution quickly for these kinds of errors.
... View more