You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Anisha Agarwal <aa...@hexiscyber.com> on 2014/08/15 19:58:59 UTC
client vs slave
Hi,
I was looking at the code to understand how a slave component differs from a client component.
1. Is there a rest call to specify that the component is a client while creating it?
2. I can see the flag on the js side of the code, but how does the server differentiate among these? I don’t see anything in the REST APIs which say whether a component is a client or a slave.
Is there anything else which I need to know when creating a client component?
Thanks,
Anisha
Re: client vs slave
Posted by Sumit Mohanty <sm...@hortonworks.com>.
Whether a component is client or a slave is driven by the metainfo.xml for
the service type in the stack definition.
On Fri, Aug 15, 2014 at 10:58 AM, Anisha Agarwal <aa...@hexiscyber.com>
wrote:
> Hi,
>
> I was looking at the code to understand how a slave component differs
> from a client component.
>
> 1. Is there a rest call to specify that the component is a client
> while creating it?
> 2. I can see the flag on the js side of the code, but how does the
> server differentiate among these? I don’t see anything in the REST APIs
> which say whether a component is a client or a slave.
>
> Is there anything else which I need to know when creating a client
> component?
>
> Thanks,
> Anisha
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.