[
https://issues.apache.org/jira/browse/AMBARI-14301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062763#comment-15062763
]
Jaimin D Jetly commented on AMBARI-14301:
-----------------------------------------
[~lavjain]
{quote}
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.
{quote}
I was not aware of Ambari still using JS code to provide initial recommendation
for host component layout . Thanks for bringing it to notice. I have created
AMBARI-14427 to address the issue.
The patch submitted on reviewboard for this ticket looks good to me (+1 to the
patch). But I will urge to migrate the logic in stack advisor. There are more
than one advantages of doing so.
# Master component (HAWQ Master and HAWQ Standby Master) host recommendation
and validation is already being done via stack advisor. Doing the same for
HAWQ Segment means all the logic for recommendation and validation will lie at
one place i.e in stack advisor
# The work done in stack advisor can be directly leveraged by Blueprint. (Note:
Blueprint is now integrated to stack advisor)
# As of now with this patch, JS changes has been done to have HAWQ Segment
initially selected with Datanode but If user explicitly chooses to add HAWQ
segment on a host that does not have DataNode or removes it from the host that
has DataNode then Ambari does not do any validation for showing any warning or
error. This can be achieved via stack advisor.
# The logic become stack driven and UI code will not have more service specific
code
I do understand that going stack advisor way means that you will get blocked by
AMBARI-14427 resolution. I will try to make that ticket actionable at the
earliest if this suggestion seems good to you.
> 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.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)
