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

Hudson commented on AMBARI-14301:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4126 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4126/])
AMBARI-14301: Co-locate HAWQSEGMENT on hosts that have DATANODE (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe8a8d1e1626a5a2f294622174f34cb0f65543fe])
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* 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: https://issues.apache.org/jira/browse/AMBARI-14301
>             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
(v6.3.4#6332)

Reply via email to