Member since
09-12-2016
39
Posts
45
Kudos Received
4
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2614 | 09-20-2016 12:17 PM | |
18814 | 09-19-2016 11:18 AM | |
2041 | 09-15-2016 09:54 AM | |
3675 | 09-15-2016 07:39 AM |
09-25-2016
02:36 PM
OK got it now, The restriction was on the Docker host service level. Just shift the Memory slider and then you should be fine.
... View more
09-20-2016
11:03 AM
1 Kudo
@ Nitin ROOT CAUSE:-
There
should be a table named by namespace for maintaining the info of tables, which
is already exists on /hbase directory , While starting the process HMaster it
will create the namespace directory under /hbase directory So it is showing the
Table Exists Exception.
SOLUTION:-
We have to
manually repair the /hbase metastore by using offline command as,
$HBASE_HOME/bin/hbase
org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair
Then start
the process of HMASTER. IF this is not working Use the zookeeper client for
removing it as,
From the
Hbase docker or any one of the docker.
zookeeper-3.4.6/bin/zkCli.sh
-server 192.168.1.90
ls /
rmr /hbase
ls /
exit
zookeeper-3.4.6/bin/zkCli.sh
-server 192.168.1.91
ls /
exit
... View more
09-05-2017
11:53 PM
Thank you for the tutorial.In my multinode hadoop installation everything is working fine except when I run start-yarn.sh.My resource manager started on master node correctly but on name nodes I am not able to see any nodemanager. When I checked my log files I saw the following errors "NodeManager doesn't satisfy minimum allocations".Similary I have also seen this in my log file "Initialized nodemanager for null: physical-memory=-1 virtual-memory=-2 virtual-cores=-1" I have no idea why its initializing with these values can you please help me to figure out this issue.?
... View more