hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API
Date Tue, 28 Apr 2015 09:14:06 GMT

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

Steve Loughran commented on YARN-3539:

+1 for consolidating the patches, including a declaration that the ATS v1 API is considered
a REST API for which compatibility will be maintained.

# is is critical to declare that ATSv1 is stable. Without that guarantee, it is impossible
for any application to commit to using the APIs. Even mapreduce is in trouble if you attempt
to run an older version of an MR app against a more recent version of the cluster, e.g a 2.6
version against a 2.7.1 Hadoop cluster.

# ATS v2 may add more options, failover etc. There's no way the existing (shipping) clients
& REST clients can access these features. What is essential is that all the existing operations
must not change, so that shipping applications do not break.

Spark depends on this for the SPARK-1537 feature, some ongoing worth with Accumulo depends
on this, when Slider adds ATS support we'll depend on this stability guarantee, etc, etc.

> Compatibility doc to state that ATS v1 is a stable REST API
> -----------------------------------------------------------
>                 Key: YARN-3539
>                 URL: https://issues.apache.org/jira/browse/YARN-3539
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-11826-001.patch, HADOOP-11826-002.patch, YARN-3539-003.patch
> The ATS v2 discussion and YARN-2423 have raised the question: "how stable are the ATSv1
> The existing compatibility document actually states that the History Server is [a stable
REST API|http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#REST_APIs],
which effectively means that ATSv1 has already been declared as a stable API.
> Clarify this by patching the compatibility document appropriately

This message was sent by Atlassian JIRA

View raw message