Thank you for the clarification. Here is my another question. If two different clients ordered "move to trash" with different interval, (e.g. client #1 with fs.trash.interval = 60; client #2 with fs.trash.interval = 120) what would happen?
Does namenode keep track of all these info? /Taeho On 3/20/08, dhruba Borthakur <[EMAIL PROTECTED]> wrote: > > The "trash" feature is a client side option and depends on the client > configuration file. If the client's configuration specifies that "Trash" > is enabled, then the HDFS client invokes a "rename to Trash" instead of > a "delete". Now, if "Trash" is enabled on the Namenode, then the > Namenode periodically removes contents from the Trash directory. > > This design might be confusing to some users. But it provides the > flexibility that different clients in the cluster can have either Trash > enabled or disabled. > > Thanks, > dhruba > > -----Original Message----- > From: Taeho Kang [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 19, 2008 3:13 AM > To: [EMAIL PROTECTED]; core-user@hadoop.apache.org; > [EMAIL PROTECTED] > Subject: Trash option in hadoop-site.xml configuration. > > Hello, > > I have these two machines that acts as a client to HDFS. > > Node #1 has Trash option enabled (e.g. fs.trash.interval set to 60) > and Node #2 has Trash option off (e.g. fs.trash.interval set to 0) > > When I order file deletion from Node #2, the file gets deleted right > away. > while the file gets moved to trash when I do the same from Node #1. > > This is a bit of surprise to me, > because I thought Trash option that I have set in the master node's > config > file > applies to everyone who connects to / uses the HDFS. > > Was there any reason why Trash option was implemented in this way? > > Thank you in advance, > > /Taeho >
