Thanks Sumit, 
Currently we are using this to run service check;
http://hdp004-1:8081/api/v1/clusters/C1/requests {"RequestInfo": 
{"command": "OOZIE_SERVICE_CHECK", "context": "OOZIE Service Check"}, 
"Requests/resource_filters": [{"service_name": "OOZIE"}]}

Ultimately what I am trying to do is programmatically create a new 
hostgroup that has just the hostname that runs the service check.
Mike




On 12/5/14, 11:55 PM, "Sumit Mohanty" <[email protected]> wrote:

>Nope, each call may vary as to which host it will execute.
>When you execute service check the request details tells you what host is
>used for that specific execution.
>
>It could be possible that when service check is triggered through the REST
>API it may take a parameter to influence the hostname. I do not remember
>the syntax for the API call to verify if its possible. I can do some
>experiments later and see if thats possible.
>
>On Fri, Dec 5, 2014 at 3:33 PM, Harp, Michael <[email protected]>
>wrote:
>
>> So if the cluster has 10 hosts with oozie clients there is no way to
>> predict? Any kind of dummy service check api call just to get the 
>>hostname?
>> Thanks,
>> Mike
>>
>>
>>
>>
>>
>> On 12/5/14, 11:19 PM, "Sumit Mohanty" <[email protected]> wrote:
>>
>> >Service check for service X runs on a randomly selected active host 
>>where
>> >a
>> >CLIENT component of service X exists. So OOZIE_SERVICE_CHECK will run 
>>on a
>> >host with OOZIE_CLIENT.
>> >
>> >thanks
>> >-Sumit
>> >
>> >On Fri, Dec 5, 2014 at 3:15 PM, Harp, Michael 
>><[email protected]>
>> >wrote:
>> >
>> >> Is there a way to determine which host is selected to run service
>> >>checks?
>> >> I am currently looking at OOZIE_SERVICE_CHECK if it is service
>> >>dependent.
>> >> Thanks,
>> >> Mike
>> >>
>> >
>> >--
>> >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.
>>
>
>-- 
>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.

Reply via email to