ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
Date Fri, 09 Sep 2016 01:12:20 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475527#comment-15475527
] 

Hudson commented on AMBARI-18345:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5641 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5641/])
AMBARI-18345. 'Stack advisor' validation code reports error while trying (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7091fc2d1eb374d8897516cbdd45f918ae997057])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py


> 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb'
config.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18345
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18345
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>             Fix For: 2.4.1
>
>         Attachments: AMBARI-18345.patch
>
>
> 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb"
config.
> *Reason:* 
> - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'.
The config may not be passed in services[configurations], depending on which action triggered
the validation. 
> - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to
query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed
or not.



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

Mime
View raw message