Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 7 Oct 2015 17:00:31 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12903044.1444237200000.47900.1444237231075@Atlassian.JIRA>
In-Reply-To: <JIRA.12903044.1444237200000@Atlassian.JIRA>
References: <JIRA.12903044.1444237200000@Atlassian.JIRA>
 <JIRA.12903044.1444237200222@arcas>
Subject: [jira] [Created] (HDFS-9208) Disabling atime may fail clients like
 distCp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kihwal Lee created HDFS-9208:
--------------------------------

             Summary: Disabling atime may fail clients like distCp
                 Key: HDFS-9208
                 URL: https://issues.apache.org/jira/browse/HDFS-9208
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Kihwal Lee


When atime is disabled, {{setTimes()}} throws an exception if the passed-in atime is not -1.  But since atime is 0, distCp fails when it tries to set the mtime and atime. 

There are several options:

1) make distCp check for 0 atime and call {{setTimes()}} with -1. I am not very enthusiastic about it.
2) make NN also accept 0 atime in addition to -1, when the atime support is disabled.
3) support setting mtime & atime regardless of the atime support.  The main reason why atime is disabled is to avoid edit logging/syncing during {{getBlockLocations()}} read calls. Explicit setting can be allowed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)