I have hbase-0.94.10 version .. all my setting works fine
Here is my JPS command output
11804 HRegionServer
10784 TaskTracker
12401 HQuorumPeer
10539 SecondaryNameNode
10201 NameNode
10369 DataNode
12669 JPS
10619 JobTracker
11624 HMaster
But after 30 sec. passed and if i type JPS command again then output was -
11804 HRegionServer
10784 TaskTracker
12401 HQuorumPeer
10539 SecondaryNameNode
10201 NameNode
10369 DataNode
12669 JPS
10619 JobTracker
Looks like HMaster is missing and because of this i am not able to access hbase master-status on web browser
Anyhelp please ..
Thanks
One of the issue could be stale zookeeper data. Try to remove zookeeper data and restart HBase.
Go to the logs.
Run HBase at debug level and try starting the master. Search for Exception.
Related
While giving Command jps :
it is showing only
some _pid jps
not showing services others likes
Namenode
Datanode
ResourceManager
etc
Have you started the service. If services is not started it will not show anything. To start the service use start-all.sh, than check jps
I am trying to run a simple job on hadoop in pseudo distribute mode.
I only have a single machine and I would like to run using yarn a simple word count.
I run the application and it doesn't run, if I check the ResourceManager I think that I understand the problem, I don't have any vcore allocated.
When I check the status of the application I am running the status is
ACCEPTED: waiting for AM container to be allocated, launched and register with RM.
I believe that the problem is just to allocate a single vcore and some RAM, but I have no idea how to achieve this...
user#user:~/hadoop-2.6.1$ jps
18420 Jps
11076 NameNode
8772 DataNode
15786 NodeManager
11296 SecondaryNameNode
16652 ResourceManager
simo#simo:~/hadoop-2.6.1$ jps
11076 NameNode
8772 DataNode
15786 NodeManager
11296 SecondaryNameNode
18881 Jps
16652 ResourceManager
The problem was lack of physical space on my HD
when i give the command
for service in /etc/init.d/hadoop*
>do
>sudo $service stop
>done
its stops all the service
and when i give
for service in /etc/init.d/hadoop-hdfs-*
>do
>sudo $service stop
>done
its stops all the service
it sometimes start datanode and sometimes namenode
eg:
21270 NameNode
21422 Jps
21374 SecondaryNameNode
2624 HMaster
or
11070 DataNode
11422 Jps
11554 SecondaryNameNode
2554 HMaster
same thing happens for jobtracker and tasktracker
I tried formating the namenode but it didnt help
I also changing the path of localhost in
core-site.xml from 8020 to 50020
and also in mapred-site.xml from 8021 to 50020
this time it shows NameNode, DataNode, JobTracker,Tasktracker using jps
but when i check the browser localhost:50070 and localhost:50030
it refers to 8020 instead of 50020.
why is this happening ?
please help
Run the following script from terminal to stop the running hadoop daemons.
> $HADOOP_INSTALL/hadoop/bin/stop-all.sh
Run the following script from terminal to start the hadoop daemons.
$HADOOP_INSTALL/hadoop/bin/start-all.sh
It seems I have no jobtracker with Hadoop 2.2.0. JPS does not show it, there is no one listening on port 50030, and there are no logs about the jobtracker inside the logs folder. Is this because of YARN? How can I configure and start the job tracker?
If you are using YARN framework, there is no jobtracker in it. Its functionality is split and replaced by ResourceManager and ApplicationMaster. Here is expected jps prinout while running YARN
$jps
18509 Jps
17107 NameNode
17170 DataNode
17252 ResourceManager
17309 NodeManager
17626 JobHistoryServer
I am running Apache Hadoop version 1.0.4.
I followed a tutorial here: http://www.michael-noll.com/tutorials/running-hadoop-on-ubuntu-linux-single-node-cluster/ with some tweaks to set up Hadoop.
The data node starts when I use the script start-dfs.sh but dies after some time (less then a second).
hduser#mudit-Studio-1535:/usr/local/hadoop/bin$ jps
25672 NameNode
26276 SecondaryNameNode
25970 DataNode
26328 Jps
hduser#mudit-Studio-1535:/usr/local/hadoop/bin$ jps
25672 NameNode
26276 SecondaryNameNode
26360 Jps
Similar problem is encountered when I use start-all.sh
I tried formatting the namenode by ./hadoop namenode -format. The output is
Still I am getting the same problem.