You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleksandr Diachenko (JIRA)" <ji...@apache.org> on 2015/10/20 00:11:27 UTC
[jira] [Commented] (AMBARI-13479) Handle derivation of hawq's yarn
related parameters where yarn is not configured
[ https://issues.apache.org/jira/browse/AMBARI-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964150#comment-14964150 ]
Oleksandr Diachenko commented on AMBARI-13479:
----------------------------------------------
+1 on the patch.
> Handle derivation of hawq's yarn related parameters where yarn is not configured
> --------------------------------------------------------------------------------
>
> Key: AMBARI-13479
> URL: https://issues.apache.org/jira/browse/AMBARI-13479
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: trunk
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Attachments: AMBARI-13479.patch
>
>
> In ambari-web/app/utils/configs/config_property_helper.js, the value of masterComponentHostsInDB.findProperty('component', 'RESOURCEMANAGER').hostName is calculated irrespective if Yarn resourcemanager is configured or not. In cases, where Yarn resourcemanager is not configured, masterComponentHostsInDB.findProperty('component', 'RESOURCEMANAGER') will result in undefined and will eventually result in Uncaught TypeError while trying to get the value of hostName.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)