You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Christopher Jackson <ja...@gmail.com> on 2015/05/18 22:28:21 UTC

co-locate tag in metainfo.xml file for custom service not working as expected.

Hi All,

I have created a custom Ambari Service with a master and client component. I have the requirement that my master component be installed on the same node that has an instance of the OOZIE/OOZIE_SERVER component. I have tried to force this by including the following snippet in my services master component configuration as part of the meta-info.xml file. However when I go to create a new cluster, my master component is placed on a node that doesn’t have OOZIE_SERVER component.

<dependency>
	<name>OOZIE/OOZIE_SERVER</name>
	<scope>host</scope>
	<auto-deploy>
		<enabled>true</enabled>
		<co-locate>MY_SERVICE/MY_MASTER_COMPONENT</co-locate>
	</auto-deploy>
</dependency>


Is this not the correct way to enforce such a requirement? Or am I missing some additional configuration?

Thanks in advance,

Christopher Jackson

Re: co-locate tag in metainfo.xml file for custom service not working as expected.

Posted by Christopher Jackson <ja...@gmail.com>.
I am installing via the UI. Not only am I having a problem forcing the two masters to be installed on the same node, but also I am having a problem with client components not being installed in the correct order. Is there a way to enforce the order in which clients get installed? My custom service has listed two client components (HBASE_CLIENT, HDFS_CLIENT) as dependencies. I would think that this would ensure they get installed first but that doesn’t seem to be the case. 

Regards,

Christopher Jackson

> On May 18, 2015, at 7:14 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> 
> Hi Christopher,
> 
> How are you creating your cluster?  Is it via UI or Blueprint API or
> granular API?
> 
> Yusaku
> 
> On 5/18/15 1:28 PM, "Christopher Jackson"
> <ja...@gmail.com> wrote:
> 
>> Hi All,
>> 
>> I have created a custom Ambari Service with a master and client
>> component. I have the requirement that my master component be installed
>> on the same node that has an instance of the OOZIE/OOZIE_SERVER
>> component. I have tried to force this by including the following snippet
>> in my services master component configuration as part of the
>> meta-info.xml file. However when I go to create a new cluster, my master
>> component is placed on a node that doesn¹t have OOZIE_SERVER component.
>> 
>> <dependency>
>> 	<name>OOZIE/OOZIE_SERVER</name>
>> 	<scope>host</scope>
>> 	<auto-deploy>
>> 		<enabled>true</enabled>
>> 		<co-locate>MY_SERVICE/MY_MASTER_COMPONENT</co-locate>
>> 	</auto-deploy>
>> </dependency>
>> 
>> 
>> Is this not the correct way to enforce such a requirement? Or am I
>> missing some additional configuration?
>> 
>> Thanks in advance,
>> 
>> Christopher Jackson
>

Re: co-locate tag in metainfo.xml file for custom service not working as expected.

Posted by Christopher Jackson <ja...@gmail.com>.
Via UI. 

Regards,

Christopher Jackson


> On May 18, 2015, at 7:14 PM, Yusaku Sako <yu...@hortonworks.com> wrote:
> 
> Hi Christopher,
> 
> How are you creating your cluster?  Is it via UI or Blueprint API or
> granular API?
> 
> Yusaku
> 
> On 5/18/15 1:28 PM, "Christopher Jackson"
> <ja...@gmail.com> wrote:
> 
>> Hi All,
>> 
>> I have created a custom Ambari Service with a master and client
>> component. I have the requirement that my master component be installed
>> on the same node that has an instance of the OOZIE/OOZIE_SERVER
>> component. I have tried to force this by including the following snippet
>> in my services master component configuration as part of the
>> meta-info.xml file. However when I go to create a new cluster, my master
>> component is placed on a node that doesn¹t have OOZIE_SERVER component.
>> 
>> <dependency>
>>    <name>OOZIE/OOZIE_SERVER</name>
>>    <scope>host</scope>
>>    <auto-deploy>
>>        <enabled>true</enabled>
>>        <co-locate>MY_SERVICE/MY_MASTER_COMPONENT</co-locate>
>>    </auto-deploy>
>> </dependency>
>> 
>> 
>> Is this not the correct way to enforce such a requirement? Or am I
>> missing some additional configuration?
>> 
>> Thanks in advance,
>> 
>> Christopher Jackson
>

Re: co-locate tag in metainfo.xml file for custom service not working as expected.

Posted by Yusaku Sako <yu...@hortonworks.com>.
Hi Christopher,

How are you creating your cluster?  Is it via UI or Blueprint API or
granular API?

Yusaku

On 5/18/15 1:28 PM, "Christopher Jackson"
<ja...@gmail.com> wrote:

>Hi All,
>
>I have created a custom Ambari Service with a master and client
>component. I have the requirement that my master component be installed
>on the same node that has an instance of the OOZIE/OOZIE_SERVER
>component. I have tried to force this by including the following snippet
>in my services master component configuration as part of the
>meta-info.xml file. However when I go to create a new cluster, my master
>component is placed on a node that doesn¹t have OOZIE_SERVER component.
>
><dependency>
>	<name>OOZIE/OOZIE_SERVER</name>
>	<scope>host</scope>
>	<auto-deploy>
>		<enabled>true</enabled>
>		<co-locate>MY_SERVICE/MY_MASTER_COMPONENT</co-locate>
>	</auto-deploy>
></dependency>
>
>
>Is this not the correct way to enforce such a requirement? Or am I
>missing some additional configuration?
>
>Thanks in advance,
>
>Christopher Jackson