You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Doroszlai, Attila (JIRA)" <ji...@apache.org> on 2017/12/13 06:29:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Doroszlai, Attila updated AMBARI-22638:
---------------------------------------
    Attachment: AMBARI-22638.trunk.001.patch

> 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)