You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2014/11/19 20:53:34 UTC
[jira] [Updated] (YARN-2879) Compatibility validation between YARN
2.2/2.4 and 2.6
[ https://issues.apache.org/jira/browse/YARN-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhijie Shen updated YARN-2879:
------------------------------
Description:
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 2.2 || MR 2.2 + Shuffle 2.6 || MR 2.4 + Shuffle 2.4 || MR 2.4 + Shuffle 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.
was:
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 2.2 || MR 2.2 + Shuffle 2.6 || MR 2.4 + Shuffle 2.4 || MR 2.4 + Shuffle 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 shuffle handler version.
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.
> 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 2.2 || MR 2.2 + Shuffle 2.6 || MR 2.4 + Shuffle 2.4 || MR 2.4 + Shuffle 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)