hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7447) Fix a couple of issues in services REST API
Date Tue, 07 Nov 2017 16:13:00 GMT

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

Billie Rinaldi commented on YARN-7447:

We don't need reflection to load YarnJacksonJaxbJsonProvider, since it is already available
with the hadoop-yarn-common dependency. I am not sure if using this provider will change the
behavior of other RMWebApp endpoints.

> Fix a couple of issues in services REST API
> -------------------------------------------
>                 Key: YARN-7447
>                 URL: https://issues.apache.org/jira/browse/YARN-7447
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-native-services
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-7447.001.patch, YARN-7447.yarn-native-services.001.patch
> [~shanekumpf@gmail.com] brought to my attention that creating a service through the REST
API does not work unless yarn app -enableFastLaunch has previously been called. This is because
we need to set the -Dservice.libdir property for the RM daemon.
> Another difference between the REST API behavior and the CLI is that posting the http
or http-no-dns example json fails with the following, even though these examples work through
the CLI:
> {noformat}
> {"diagnostics":"For TEMPLATE format, either src_file must be specified in ConfigFile,
or the \"content\" key must be specified in the properties field of ConfigFile. "}
> {noformat}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message