HI dear,
actually I noticed that when I shut down the VM and restarted
but quite weird, I was able to see datanote appearing before I shut down
after logging in again, I invokved the command ../start_dfs.sh
it started secondarynamenode and the namenode is now running at port 8020
as against 9000
sudo jps reveals the below:
1718 NameNode
4840 SecondaryNameNode
1902 JobHistoryServer
4681 DataNode
1786 ResourceManager
4953 Jps
1841 NodeManager
the issue now is, whereas core-site.xml is configured with port 9000, whereas curretnly after running start-dfs.sh command the namenode now is running at port 8020, hence probably I will have to change the port details in core-site.xml
Hi
sorry that did not work :)
I am getting the below error
ogging initialized using configuration in jar:file:/home/edureka/raghu/MyHiveHome/apache-hive-2.1.1-bin/lib/hive-common-2.1.1.jar!/hive-log4j2.properties Async: true
Exception in thread 'main' java.lang.RuntimeException: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.server.namenode.SafeModeException): Cannot create directory /tmp/hive. Name node is in safe mode.
The reported blocks 0 needs additional 38 blocks to reach the threshold 0.9990 of total blocks 38.
Safe mode will be turned off automatically
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirsInt(FSNamesystem.java:3355)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3330)
hence I will have to ensure that the namenode shows up on port 9000 when I invoke the URL : http://localhost:50070/dfshealth.jsp
