in case anybody has some idea on what I should look for in debugging this..
below is a strace of the simple bin/hadoop dfs -ls / command run on the
machine running namenode
% time seconds usecs/call callserrors syscall
-- --- --- - -
Hi Gopi,
Check if you can run groups -F hduser. I think it's causing the delay.
Daryn
On Mar 31, 2013, at 1:17 AM, Gopi Krishna M wrote:
Hi..
I have installed hadoop 0.23.5 and is working fine on two of my installations.
In a new installation on Windows Azure VMs, I am seeing an inordinate
just tried the command. returns instantaneously, no delay
~/installations/hadoop-0.23.5$ groups hduser
hduser : hduser
ps: -F option is not working.
On Thu, Apr 4, 2013 at 6:29 PM, Daryn Sharp da...@yahoo-inc.com wrote:
Hi Gopi,
Check if you can run groups -F hduser. I think it's
Gopi,
The namenode is essentially running bash -c id -Gn hduser and waiting for the
response. You could try executing from the shell it to see if it does take a
long time in Azure, or if the output is too complex to parse.
Regards,
Marcos
In 04-04-2013 09:33, Gopi Krishna M wrote:
in case
Hi Marcos,
executed it from shell.. returns immediately, no delay and the output is
just hduser..
hduser@hmaster-asia:~/installations/hadoop-0.23.5$ bash -c id -Gn hduser
hduser
one important thing I noticed on logs is (posted in my first mail), it
always get stuck *twice for exactly 60secs*.
Hi..
I have installed hadoop 0.23.5 and is working fine on two of my
installations. In a new installation on Windows Azure VMs, I am seeing an
inordinate delay (of 1 minute) when doing a simple dfs ls command.
This is a 3 node cluster, running 64 bit Ubuntu 12.04.1 LTS, Sun jre
command :
