[ 
https://issues.apache.org/jira/browse/AMBARI-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bhuvnesh chaudhary updated AMBARI-14621:
----------------------------------------
    Description: 
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.

  was:
Blueprint deploy should update the value localhost for HAWQMASTER and 
HAWQSTANDBY with the name of the namenode hostname.

The logic to replace the hostname is currently only on the Web UI due to which 
during deploy, hawq_master_address_host and hawq_standby_address_host are set 
to localhost and hawq start fails. 


> 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
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-14621-branch-2.2.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)

Reply via email to