-grep edit", right?
By the way, the version of the cluster is hadoop 2.2.0. I have no idea if this
information helpful.
Thanks
From: ha...@cloudera.com
Date: Mon, 23 May 2016 03:33:17 +
Subject: Re: No edits files in dfs.namenode.edits.dir
To: sky880883...@hotmail.com; gurmukh.dhil...@y
gt;
> If really no edits persist to disk, any idea about how to fix this problem?
>
> thanks
> ------
> Subject: Re: No edits files in dfs.namenode.edits.dir
> To: ravihad...@gmail.com; sky880883...@hotmail.com
> CC: user@hadoop.apache.org
> Fro
problem?
thanks
Subject: Re: No edits files in dfs.namenode.edits.dir
To: ravihad...@gmail.com; sky880883...@hotmail.com
CC: user@hadoop.apache.org
From: gurmukh.dhil...@yahoo.com.INVALID
Date: Sun, 22 May 2016 21:45:50 +1000
Have you explicitly configured the parameter
&
Have you explicitly configured the parameter "dfs.namenode.edits.dir" ?
else it default to dfs.namenode.name.dir
On 20/05/16 4:46 AM, Ravi Prakash wrote:
No! You are probably writing the edits file somewhere still. An `lsof`
on the namenode process may be more revealing. Obviously this
No! You are probably writing the edits file somewhere still. An `lsof` on
the namenode process may be more revealing. Obviously this depends on
configuration, but unless you have some really crazy settings, I'm pretty
sure the edits would be persisted to disk.
On Wed, May 18, 2016 at 2:47 AM,
Hi, I found that there is no edits file in my cluster's dfs.namenode.edits.dir.
It is a 20-nodes cluster without secondary namenode, and it runs well for a
long while (more than one year).
However, it's found that no edits file in the dfs.namenode.edits.dir and the
the fsimage file doesn't
