Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Sat, 1 Dec 2012 23:23:58 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <1922454967.49886.1354404238241.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HDFS-4258) Rename of Being Written Files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tsz Wo (Nicholas), SZE created HDFS-4258:
--------------------------------------------

             Summary: Rename of Being Written Files
                 Key: HDFS-4258
                 URL: https://issues.apache.org/jira/browse/HDFS-4258
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs-client, namenode
            Reporter: Tsz Wo (Nicholas), SZE


When a being written file or it's ancestor directories is renamed, the path in the file lease is also renamed.  Then the writer of the file usually will fail since the file path in the writer is not updated.

Moreover, I think there is a bug as follow:

# Client writes 0's to F_0="/foo/file" and writes 1's to F_1="/bar/file" at the same time.
# Rename /bar to /baz
# Rename /foo to /bar

Then, writing to F_0 will fail since /foo/file does not exist anymore but writing to F_2 may succeed since /bar/file exits as a different file.  In such case, the content of /bar/file could be partly 0's and partly 1's.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira