[
https://issues.apache.org/jira/browse/HADOOP-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035786#comment-13035786
]
Aaron T. Myers commented on HADOOP-7287:
----------------------------------------
HDFS tests which failed:
org.apache.hadoop.tools.TestJMXGet
org.apache.hadoop.hdfs.server.namenode.TestBlocksWithNotEnoughRacks
org.apache.hadoop.hdfs.TestDecommission
org.apache.hadoop.hdfs.TestDatanodeBlockScanner
org.apache.hadoop.hdfs.TestHDFSTrash
All of which, I believe, are known to be flaky or failing. I was able to run
TestBlocksWithNotEnoughRacks, TestDecommission, and TestDatanodeBlockScanner
individually, and they passed.
Running the M/R tests now.
> Configuration deprecation mechanism doesn't work properly for
> GenericOptionsParser/Tools
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-7287
> URL: https://issues.apache.org/jira/browse/HADOOP-7287
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Assignee: Aaron T. Myers
> Priority: Blocker
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hadoop-7287-testcase.txt, hadoop-7287-trunk.0.patch
>
>
> For example, you can't use -D options on the "hadoop fs" command line in
> order to specify the deprecated names of configuration options. The issue is
> that the ordering is:
> - JVM starts
> - GenericOptionsParser creates a Configuration object and calls set() for
> each of the options specified on command line
> - DistributedFileSystem or other class eventually instantiates
> HdfsConfiguration which adds the deprecations
> - Some class calls conf.get("new key") and sees the default instead of the
> version set on the command line
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
