Thanks Joey, So this means, I edit the hdfs-site.xml file to reflect the empty directory, restart the namenode.
Will Namenode populate all the metadata to the newly added directory ? Just wanted to make sure I do everything right. While googling, I also noticed issues when one of the directories becomes unavailable (NFS mount), HDFS hangs, is this still true ? https://groups.google.com/a/cloudera.org/group/cdh-user/msg/aa014cf61dc2daae? -----Original Message----- From: Joey Echeverria [mailto:j...@cloudera.com] Sent: Tuesday, January 31, 2012 4:15 PM To: hdfs-user@hadoop.apache.org Subject: Re: Adding dfs.name.dir You need to restart the namenode for the new setting to take effect. The namenode will be unavailable for a while during the restart. -Joey On Tue, Jan 31, 2012 at 5:26 PM, Jain, Prem <premanshu.j...@netapp.com> wrote: > Team, > > I would like to add additional directory under "dfs.name.dir" property > in order to have one more copy of namenode metadata. My HDFS is > already running and in production. > > Is there a clean way to do this ? > > Thanks in advance > > > > > > -- Joseph Echeverria Cloudera, Inc. 443.305.9434
