ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-14301) Co-locate HAWQSEGMENT on hosts that have DATANODE component
Date Wed, 06 Jan 2016 06:53:40 GMT


Hudson commented on AMBARI-14301:

ABORTED: Integrated in Ambari-trunk-Commit #4126 (See [])
AMBARI-14301: Co-locate HAWQSEGMENT on hosts that have DATANODE (jaoki: [])
* ambari-server/src/test/python/stacks/2.3/common/
* ambari-server/src/main/resources/stacks/HDP/2.3/services/
* ambari-server/src/test/python/stacks/2.3/common/services-hawq-pxf-hdfs.json
* ambari-server/src/test/python/stacks/2.3/common/services-pxf-hdfs.json

> Co-locate HAWQSEGMENT on hosts that have DATANODE component 
> ------------------------------------------------------------
>                 Key: AMBARI-14301
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-web
>    Affects Versions: trunk
>            Reporter: Lav Jain
>            Assignee: Lav Jain
>            Priority: Minor
>             Fix For: 2.3.0
>         Attachments: AMBARI-14301-2.patch, AMBARI-14301.patch, AMBARI-14301.patch
> Looks like stackadvisor is used only upon a fresh install if no changes are made to the
master components. In that case, the client/slaves are installed on all the hosts, so HAWQSEGMENT
is co-located with DATANODE by default.
> If HDFS is already installed and HAWQ is enabled using add services, then Ambari chooses
all hosts that do not have a MASTER component installed. This determination is being done
in the javascript code.
> This patch is changing the hostlist for HAWQSEGMENT to be the same as DATANODE in the
latter case.

This message was sent by Atlassian JIRA

View raw message