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

Zhijie Shen commented on YARN-2879:
-----------------------------------

In the following scenarios:

1. Either insecure or secure;
2. MR 2.2 with new shuffle on NM;
3. Submitting via old client.

We will see the following console exception:
{code}
Console Log:
14/11/17 14:56:19 INFO mapreduce.Job: Job job_1416264695865_0003 completed 
successfully
java.lang.IllegalArgumentException: No enum constant 
org.apache.hadoop.mapreduce.JobCounter.MB_MILLIS_REDUCES
        at java.lang.Enum.valueOf(Enum.java:236)
        at 
org.apache.hadoop.mapreduce.counters.FrameworkCounterGroup.valueOf(FrameworkCounterGroup.java:148)
        at 
org.apache.hadoop.mapreduce.counters.FrameworkCounterGroup.findCounter(FrameworkCounterGroup.java:182)
        at 
org.apache.hadoop.mapreduce.counters.AbstractCounters.findCounter(AbstractCounters.java:154)
        at 
org.apache.hadoop.mapreduce.TypeConverter.fromYarn(TypeConverter.java:240)
        at 
org.apache.hadoop.mapred.ClientServiceDelegate.getJobCounters(ClientServiceDelegate.java:370)
        at 
org.apache.hadoop.mapred.YARNRunner.getJobCounters(YARNRunner.java:511)
        at org.apache.hadoop.mapreduce.Job$7.run(Job.java:756)
        at org.apache.hadoop.mapreduce.Job$7.run(Job.java:753)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:415)
        at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1491)
        at org.apache.hadoop.mapreduce.Job.getCounters(Job.java:753)
        at org.apache.hadoop.mapreduce.Job.monitorAndPrintJob(Job.java:1361)
        at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1289)
        at 
org.apache.hadoop.examples.QuasiMonteCarlo.estimatePi(QuasiMonteCarlo.java:306)
        at 
org.apache.hadoop.examples.QuasiMonteCarlo.run(QuasiMonteCarlo.java:354)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
        at 
org.apache.hadoop.examples.QuasiMonteCarlo.main(QuasiMonteCarlo.java:363)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at 
org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:72)
        at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
        at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
{code}

The problem is supposed to be fixed by MAPREDUCE-5831, however, it seems that 
we haven't cover all the problematic code path. Will another Jira again.

> Compatibility validation between YARN 2.2/2.4 and 2.6
> -----------------------------------------------------
>
>                 Key: YARN-2879
>                 URL: https://issues.apache.org/jira/browse/YARN-2879
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>
> Recently, I did some simple backward compatibility experiments. Bascially, 
> I've taken the following 2 steps:
> 1. Deploy the application (MR and DistributedShell) that is compiled against 
> *old* YARN API (2.2/2.4) on *new* YARN cluster (2.6). The application is 
> submitted via *new* Hadoop (2.6) client.
> 2. Deploy the application (MR and DistributedShell) that is compiled against 
> *old* YARN API (2.2/2.4) on *new* YARN cluster (2.6). The application is 
> submitted via *old* Hadoop (2.2/2.4) client that comes with the app.
> I've tried these 2 steps on both insecure and secure cluster. Here's a short 
> summary:
> || || || DS 2.2 || DS 2.4 || MR 2.2 + Shuffle and RT 2.2 || MR 2.2 + Shuffle 
> and RT 2.6 || MR 2.4 + Shuffle and RT 2.4 || MR 2.4 + Shuffle and RT 2.6 ||
> | Insecure | New Client | OK | OK | Client Incompatible | Client Incompatible 
> | OK | OK |
> | Insecure | Old Client | OK | OK | AM Incompatible | Client Incompatible | 
> OK | OK |
> | Secure | New Client | OK | OK | Client Incompatible | Client Incompatible | 
> OK | OK |
> | Secure | Old Client | OK | OK | AM Incompatible | Client Incompatible | OK 
> | OK |
> Note that I've tried to run NM with both old and new version of shuffle 
> handler plus the runtime libs.
> In general, the compatibility looks good overall. There're a few issues that 
> are related to MR, but they seem to be not the YARN issue. I'll post the 
> individual problem in the follow-up comments.



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

Reply via email to