[ 
https://issues.apache.org/jira/browse/YARN-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643880#comment-13643880
 ] 

shenhong commented on YARN-622:
-------------------------------

My mapred-site.xml is empty.
I thank the reason is in org.apache.hadoop.conf.Configuration:
public void set(String name, String value, String source) {
    if (deprecatedKeyMap.isEmpty()) {
      getProps();
    }
    getOverlay().setProperty(name, value);
    getProps().setProperty(name, value);
    if(source == null) {
      updatingResource.put(name, new String[] {"programatically"});
    } else {
      updatingResource.put(name, new String[] {source});
    }
    String[] altNames = getAlternateNames(name);
    if (altNames != null && altNames.length > 0) {
      String altSource = "because " + name + " is deprecated";
      for(String altName : altNames) {
        if(!altName.equals(name)) {
          getOverlay().setProperty(altName, value);
          getProps().setProperty(altName, value);
          updatingResource.put(altName, new String[] {altSource});
        }
      }
    }
    warnOnceIfDeprecated(name);
  }

                
> Many deprecated warn messages in hadoop 2.0 when running sleepJob
> -----------------------------------------------------------------
>
>                 Key: YARN-622
>                 URL: https://issues.apache.org/jira/browse/YARN-622
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.0.4-alpha
>         Environment: Run a sleep job in hadoop-2.0.4-alpha
>            Reporter: shenhong
>
> hadoop jar 
> share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.0.4-alpha.jar s
> leep -m 1
> 13/04/28 10:16:46 INFO util.Shell: setsid exited with exit code 0
> 13/04/28 10:16:46 WARN conf.Configuration: session.id is deprecated. Instead, 
> use dfs.metrics.session-id
> 13/04/28 10:16:46 INFO jvm.JvmMetrics: Initializing JVM Metrics with 
> processName=JobTracker, sessionId=
> 13/04/28 10:16:46 INFO mapreduce.JobSubmitter: number of splits:1
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.jar is deprecated. Instead, 
> use mapreduce.job.jar
> 13/04/28 10:16:46 WARN conf.Configuration: 
> mapred.map.tasks.speculative.execution is deprecated. Instead, use 
> mapreduce.map.speculative
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.reduce.tasks is deprecated. 
> Instead, use mapreduce.job.reduces
> 13/04/28 10:16:46 WARN conf.Configuration: mapreduce.partitioner.class is 
> deprecated. Instead, use mapreduce.job.partitioner.class
> 13/04/28 10:16:46 WARN conf.Configuration: 
> mapred.reduce.tasks.speculative.execution is deprecated. Instead, use 
> mapreduce.reduce.speculative
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.mapoutput.value.class is 
> deprecated. Instead, use mapreduce.map.output.value.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapreduce.map.class is deprecated. 
> Instead, use mapreduce.job.map.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.job.name is deprecated. 
> Instead, use mapreduce.job.name
> 13/04/28 10:16:46 WARN conf.Configuration: mapreduce.reduce.class is 
> deprecated. Instead, use mapreduce.job.reduce.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapreduce.inputformat.class is 
> deprecated. Instead, use mapreduce.job.inputformat.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.input.dir is deprecated. 
> Instead, use mapreduce.input.fileinputformat.inputdir
> 13/04/28 10:16:46 WARN conf.Configuration: mapreduce.outputformat.class is 
> deprecated. Instead, use mapreduce.job.outputformat.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.map.tasks is deprecated. 
> Instead, use mapreduce.job.maps
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.mapoutput.key.class is 
> deprecated. Instead, use mapreduce.map.output.key.class
> 13/04/28 10:16:46 WARN conf.Configuration: mapred.working.dir is deprecated. 
> Instead, use mapreduce.job.working.dir

--
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

Reply via email to