You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "bhuvnesh chaudhary (JIRA)" <ji...@apache.org> on 2016/01/12 06:27:39 UTC
[jira] [Assigned] (AMBARI-14621) Blueprint deploy should update the
value localhost for HAWQMASTER and HAWQSTANDBY
[ https://issues.apache.org/jira/browse/AMBARI-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bhuvnesh chaudhary reassigned AMBARI-14621:
-------------------------------------------
Assignee: bhuvnesh chaudhary
> Blueprint deploy should update the value localhost for HAWQMASTER and HAWQSTANDBY
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-14621
> URL: https://issues.apache.org/jira/browse/AMBARI-14621
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
> Affects Versions: 2.2.1
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-14621-branch-2.2.patch, AMBARI-14621.patch
>
>
> Blueprint deploy should update the value localhost for HAWQMASTER, HAWQSTANDBY with the name of their respective component hostname. It should also update the value of hawq_dfs_url to NAMENODE HOST.
> The logic to replace the hostname is currently only on the Web UI due to which during deploy, hawq_master_address_host, hawq_standby_address_host and hawq_dfs_url are set to localhost and hawq start fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)