You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Christopher Jackson (JIRA)" <ji...@apache.org> on 2015/06/11 18:06:00 UTC

[jira] [Created] (AMBARI-11861) co-locate tag ignored in custom services component configuration.

Christopher Jackson created AMBARI-11861:
--------------------------------------------

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