You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/12/13 21:04:01 UTC
[jira] [Commented] (AMBARI-22638) yarn.timeline-service property
enabled overriding preset secure blueprint config for the same
[ https://issues.apache.org/jira/browse/AMBARI-22638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289908#comment-16289908 ]
Hudson commented on AMBARI-22638:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8519 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8519/])
AMBARI-22638. yarn.timeline-service property enabled overriding preset (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e46575a17d4b9877aa5a67aa87ee690c326f6a64])
* (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json
> yarn.timeline-service property enabled overriding preset secure blueprint config for the same
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-22638
> URL: https://issues.apache.org/jira/browse/AMBARI-22638
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 3.0.0
> Reporter: Kishor Ramakrishnan
> Assignee: Doroszlai, Attila
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22638.trunk.001.patch
>
>
> yarn.timeline-service property enabled overriding preset secure blueprint config for the same.
> Configuration in yarn-site in blueprint
> {code:java}
> "yarn.timeline-service.enabled": "false"
> {code}
> The same config resolved in TOPOLOGY_RESOLVED yarn-site to
> {code:java}
> "yarn.timeline-service.enabled": "true"
> {code}
> Configuration recommendation strategy in while cluster deploy template is ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES
> {code:java}
> "config_recommendation_strategy": "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> {code}
> Expected behavior: The config yarn.timeline-service.enabled should have persisted the value "false" even after deploy.
> Actual behavior: Flag "yarn.timeline-service.enabled" is toggled to "true" while resolving configs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)