[
https://issues.apache.org/jira/browse/HDFS-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175664#comment-13175664
]
Uma Maheswara Rao G commented on HDFS-2712:
-------------------------------------------
Failures looks to be due to Balancer tests time out
{quote}
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.302 sec
Running org.apache.hadoop.hdfs.server.balancer.TestBalancer
Running org.apache.hadoop.hdfs.web.TestOffsetUrlInputStream
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.567 sec
Running org.apache.hadoop.hdfs.web.TestWebHdfsFileSystemContract
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.199 sec <<<
FAILURE!
Running org.apache.hadoop.hdfs.web.TestFSMainOperationsWebHdfs
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.274 sec <<<
FAILURE!
{quote}
In recent build balancer tests has broken in Jenkins.
https://builds.apache.org/job/Hadoop-Hdfs-trunk/lastCompletedBuild/testReport/
Filed a JIRA for Balancer tests HDFS-2721
findbugs also unrelated.
> setTimes should support only for files and move the atime field down to
> iNodeFile.
> ----------------------------------------------------------------------------------
>
> Key: HDFS-2712
> URL: https://issues.apache.org/jira/browse/HDFS-2712
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Attachments: HDFS-2712.patch
>
>
> After the dicussion in HDFS-2436, unsupported behaviour for setTimes was
> intentional (HADOOP-1869).
> But current INode structure hierarchy seems, it supports atime for
> directories also. But as per HADOOP-1869, we are supporting only for files.
> To avoid the confusions, we can move the atime fields to INodeFile as we
> planned to support setTimes only for files. And also restrict the support for
> setTimes on directories ( which is implemented with HDFS-2436 ).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
