[jira] [Commented] (AMBARI-14301) Co-locate HAWQSEGMENT on hosts that have DATANODE component

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-14301:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12776643/AMBARI-14301.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4543//console

This message is automatically generated.

> 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)