Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 52406 invoked from network); 19 Mar 2008 10:13:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2008 10:13:37 -0000 Received: (qmail 78435 invoked by uid 500); 19 Mar 2008 10:13:28 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 77992 invoked by uid 500); 19 Mar 2008 10:13:27 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 77975 invoked by uid 500); 19 Mar 2008 10:13:26 -0000 Delivered-To: apmail-lucene-hadoop-user@lucene.apache.org Received: (qmail 77969 invoked by uid 99); 19 Mar 2008 10:13:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 03:13:26 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tkang1@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 10:12:48 +0000 Received: by wa-out-1112.google.com with SMTP id j40so358626wah.11 for ; Wed, 19 Mar 2008 03:12:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=OaLmC8qPRJddx3OcLzy66isC2miVc7xvsAWWl8ermzI=; b=lIz+U7Vne2yR7bLTOGw14jlGJmgRIayY1ZD/4cu9v+zitv/rIQwGWTB3D1gpHQnLWpeGtFyQKRwpo55+Cv/BpvOHhUYFeo/aPTAiPg7UGTghVe02/zwYLC5KVxtd8d1xNDDYOq8vQKMeOYypW7lZLB5A4QhMO+JkrltF1HPnF3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type; b=oEWf9z2U+v6n7zdbGvjMnz3RdaKSdc7zoPU1MrLGHK2VVyQ6MmTNHAzGtlqM23Ukgxyg3b/BSFenPnVEPkDubkax/cB3PLl3ZsRAMzAQRTp3Te3GFBjonSeTcQbFd6hf3uOINIoUgk8hHZiKMGTMxpEUKZW2OWpDW/IboAPzxfI= Received: by 10.114.195.19 with SMTP id s19mr920444waf.58.1205921579582; Wed, 19 Mar 2008 03:12:59 -0700 (PDT) Received: by 10.115.88.17 with HTTP; Wed, 19 Mar 2008 03:12:59 -0700 (PDT) Message-ID: <279a90ff0803190312t596b0c90m3caaebb94166eb91@mail.gmail.com> Date: Wed, 19 Mar 2008 19:12:59 +0900 From: "Taeho Kang" To: hadoop-user@lucene.apache.org, core-user@hadoop.apache.org, tkang1@gmail.com Subject: Trash option in hadoop-site.xml configuration. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2268_2546474.1205921579573" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2268_2546474.1205921579573 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_2268_2546474.1205921579573--