Return-Path: 
 <issues-return-1989-apmail-ambari-issues-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org
Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B3F7219CDE
	for <apmail-ambari-issues-archive@minotaur.apache.org>;
 Tue, 22 Mar 2016 20:14:25 +0000 (UTC)
Received: (qmail 27348 invoked by uid 500); 22 Mar 2016 20:14:25 -0000
Delivered-To: apmail-ambari-issues-archive@ambari.apache.org
Received: (qmail 27313 invoked by uid 500); 22 Mar 2016 20:14:25 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 27284 invoked by uid 99); 22 Mar 2016 20:14:25 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Mar 2016 20:14:25 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 844C72C14F8
	for <issues@ambari.apache.org>; Tue, 22 Mar 2016 20:14:25 +0000 (UTC)
Date: Tue, 22 Mar 2016 20:14:25 +0000 (UTC)
From: "Christopher Jackson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12837182.1434038740000.21878.1458677665539@Atlassian.JIRA>
In-Reply-To: <JIRA.12837182.1434038740000@Atlassian.JIRA>
References: <JIRA.12837182.1434038740000@Atlassian.JIRA>
 <JIRA.12837182.1434038740379@arcas>
Subject: [jira] [Commented] (AMBARI-11861) co-locate tag ignored in custom
 services component configuration.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Christopher Jackson commented on AMBARI-11861:
----------------------------------------------

Anyone care to comment on this issue? Particularly if I misunderstood this configuration property?

> co-locate tag ignored in custom services component configuration.
> -----------------------------------------------------------------
>
>                 Key: AMBARI-11861
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11861
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>         Environment: HDP 2.2, Rhel6
>            Reporter: Christopher Jackson
>
> I created a custom service with a 'master' component with the following configuration:
> <dependency>
>   <name>OOZIE/OOZIE_SERVER</name>
>   <scope>host</scope>
>   <auto-deploy>
>     <enabled>true</enabled>
>     <co-locate>MY_CUSTOM_SERVICE/CUSTOM_MASTER</co-locate>
>   </auto-deploy>
> </dependency>
> With an existing cluster I tried adding the custom service through the Ambari UI. However, the CUSTOM_MASTER component is not automatically placed on the same node that is running OOZIE_SERVER component. I believe the above configuration is meant to enforce that the MY_CUSTOM_SERVICE/CUSTOM_MASTER and OOZIE/OOZIE_SERVER components are placed on the same node, is that not true?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)