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-14301) Co-locate HAWQSEGMENT on hosts that have DATANODE component
Date Thu, 07 Jan 2016 00:39:39 GMT

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

jun aoki commented on AMBARI-14301:
-----------------------------------

Committed to branch-2.2
 d45c16b126eb0c7014cd1b78ee12035aa9480b09

> 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, 2.2.1
>
>         Attachments: AMBARI-14301-2.branch22.patch, 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)

Mime
View raw message