[jira] [Updated] (YARN-3292) [Umbrella] Tests/documentation and/or tools for YARN rolling upgrades backwards/forward compatibility verification

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated YARN-3292:
------------------------------------------
    Summary: [Umbrella] Tests/documentation and/or tools for YARN rolling upgrades backwards/forward compatibility verification  (was: [Umbrella] Tests and/or tools for YARN backwards compatibility verification)

Edited title to reflect that this is about rolling upgrades and to focus also on forward compatibility.

I'd also like to see if w can whip up a doc or two for listing general guidelines for developers in addition to our existing compatibility guide. Edited the title to also include that.

> [Umbrella] Tests/documentation and/or tools for YARN rolling upgrades backwards/forward compatibility verification
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3292
>                 URL: https://issues.apache.org/jira/browse/YARN-3292
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Li Lu
>            Assignee: Li Lu
>              Labels: compatibility, rolling_upgrade, test, tools
>
> YARN-666 added the support to YARN rolling upgrade. In order to support this feature, we made changes from many perspectives. There were many assumptions made together with these existing changes. Future code changes may break these assumptions by accident, and hence break the YARN rolling upgrades feature. 
> To simplify YARN RU regression tests, maybe we would like to create a set of tools/tests that can verify YARN RU backward compatibility. 
> On the very first step, we may want to have a compatibility checker for important protocols and APIs. We may also want to incorporate these tools into our test Jenkins runs, if necessary. 



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