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 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, sky88088 <sky880883368@hotmail.com> wrote:
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 update. 

Is it meaning that all the metadata of name node only stay in the memory?

Is there a way to fix it? Is there any configuration to control the persistence?


Thanks and Regards

Gurmukh Singh