ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jun aoki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14621) Blueprint deploy should update the value localhost for HAWQMASTER and HAWQSTANDBY
Date Wed, 13 Jan 2016 18:56:39 GMT

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

jun aoki commented on AMBARI-14621:
-----------------------------------

Committed to branch-2.2
a225f394bc4a182d45f975dafc171419bf57f559
Committed to trunk
69c3e0d0e09cae90937797da12fd10ee8004d77b

> 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-5.patch, 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)

Mime
View raw message