ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Jackson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11861) co-locate tag ignored in custom services component configuration.
Date Tue, 22 Mar 2016 20:14:25 GMT

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

Mime
View raw message