Hi Harsh,
I have made my dfs.namenode.name.dir point to a subdirectory of my home,
and I don't see this issue again. So, is this a bug that we need to log
into JIRA?
Thanks,
Kishore
On Tue, Jul 16, 2013 at 6:39 AM, Harsh J ha...@cloudera.com wrote:
2013-07-12 11:04:26,002 WARN
this is not a bug.
it has been documented.
On Jul 19, 2013 10:13 PM, Krishna Kishore Bonagiri
write2kish...@gmail.com wrote:
Hi Harsh,
I have made my dfs.namenode.name.dir point to a subdirectory of my
home, and I don't see this issue again. So, is this a bug that we need to
log into
Yeah I believe your /tmp was probably misbehaving somehow (running out
of space or otherwise). You could log a JIRA for the null seen in
the log though, it shouldn't have done that and should've shown the
real mount point.
On Fri, Jul 19, 2013 at 8:47 PM, Azuryy Yu azury...@gmail.com wrote:
this
Yes Harsh, I haven't set dfs.namenode.name.dir anywhere in config files. My
name node has again gone into safe mode today while it was idle. I shall
try setting this value to something other than /tmp
On Tue, Jul 16, 2013 at 6:39 AM, Harsh J ha...@cloudera.com wrote:
2013-07-12 11:04:26,002
Hi,
I am doing no activity on my single node cluster which is using
2.1.0-beta, and still observed that it has gone to safe mode by itself
after a while. I was looking at the name node log and see many of these
kinds of entries.. Can anything be interpreted from these?
2013-07-12 09:06:11,256
hi,
from the log:
NameNode low on available disk space. Entering safe mode.
this is the root cause.
On Jul 15, 2013 2:45 PM, Krishna Kishore Bonagiri
write2kish...@gmail.com wrote:
Hi,
I am doing no activity on my single node cluster which is using
2.1.0-beta, and still observed that it
Hi,
pls see the available space for NN storage directory.
Thanks Regards
Venkat
On Mon, Jul 15, 2013 at 12:14 PM, Krishna Kishore Bonagiri
write2kish...@gmail.com wrote:
Hi,
I am doing no activity on my single node cluster which is using
2.1.0-beta, and still observed that it has gone
I have had enough space on the disk that is used, like around 30 Gigs
Thanks,
Kishore
On Mon, Jul 15, 2013 at 1:30 PM, Venkatarami Netla
venkatarami.ne...@cloudwick.com wrote:
Hi,
pls see the available space for NN storage directory.
Thanks Regards
Venkat
On Mon, Jul 15, 2013 at
Hi Krishna,
Can you please send screenshots of namenode web UI.
Thanks Aditya.
On Mon, Jul 15, 2013 at 1:54 PM, Krishna Kishore Bonagiri
write2kish...@gmail.com wrote:
I have had enough space on the disk that is used, like around 30 Gigs
Thanks,
Kishore
On Mon, Jul 15, 2013 at 1:30
please check dfs.datanode.du.reserved in the hdfs-site.xml
On Jul 15, 2013 4:30 PM, Aditya exalter adityaexal...@gmail.com wrote:
Hi Krishna,
Can you please send screenshots of namenode web UI.
Thanks Aditya.
On Mon, Jul 15, 2013 at 1:54 PM, Krishna Kishore Bonagiri
Hi,
I have restarted my cluster after removing the data directory and
formatting the namenode. So, is this screenshot still useful for you or do
you want it only after I reproduce the issue?
Thanks,
Kishore
On Mon, Jul 15, 2013 at 1:59 PM, Venkatarami Netla
venkatarami.ne...@cloudwick.com
I don't have it in my hdfs-site.xml, in which case probably the default
value is taken..
On Mon, Jul 15, 2013 at 2:29 PM, Azuryy Yu azury...@gmail.com wrote:
please check dfs.datanode.du.reserved in the hdfs-site.xml
On Jul 15, 2013 4:30 PM, Aditya exalter adityaexal...@gmail.com wrote:
Hi
2013-07-12 11:04:26,002 WARN
org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
available on volume 'null' is 0, which is below the configured reserved
amount 104857600
This is interesting. Its calling your volume null, which may be more
of a superficial bug.
What is
hi
what you dfs.namenode.name.dir set?
check you dfs,namenode.name.dir directory permit and make sure you user can
access
2013/7/16 Harsh J ha...@cloudera.com
2013-07-12 11:04:26,002 WARN
org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
available on volume 'null' is 0,
14 matches
Mail list logo
