Victor,

could you please describe your case in details? I would like to understand
why standard mesos health checks won't suit your case.

On Wed, Sep 14, 2016 at 8:15 AM, haosdent <haosd...@gmail.com> wrote:

> Hi, @Victor taskId is specified in `TaskInfo` when you launchTask.
>
> On Wed, Sep 14, 2016 at 6:22 AM, Victor L <vlyamt...@gmail.com> wrote:
>
>> how can i get taskId to call "killTask"?
>>
>> On Tue, Sep 13, 2016 at 9:59 AM, haosdent <haosd...@gmail.com> wrote:
>>
>>> If you want to kill the task from the scheduler, you just need to call
>>> `killTask`(https://github.com/apache/mesos/blob/1.0.x/includ
>>> e/mesos/scheduler.hpp#L257).
>>> If you want to kill the task by health check, you could try to set the
>>> correct `consecutive_failures` number (https://github.com/apache/mes
>>> os/blob/1.0.x/include/mesos/v1/mesos.proto#L358).
>>>
>>> On Tue, Sep 13, 2016 at 2:53 AM, Victor L <vlyamt...@gmail.com> wrote:
>>>
>>>> How can i explicitly kill the task from my class?
>>>>
>>>> On Mon, Sep 12, 2016 at 2:10 PM, haosdent <haosd...@gmail.com> wrote:
>>>>
>>>>> If the target you perform health check is your task, Mesos support
>>>>> health check by a command. When your task reaches the health task failure
>>>>> limit, the task would be killed and then your framework could launch the
>>>>> task again when receives the `TASK_KILLED` in `statusUpdate`.
>>>>>
>>>>> On Tue, Sep 13, 2016 at 2:03 AM, Victor L <vlyamt...@gmail.com> wrote:
>>>>>
>>>>>> It checks if process is functional. I don't think standard
>>>>>> healthchecks wouldn't be sufficient for my purpose and my question still
>>>>>> stands: how  to use result...
>>>>>>
>>>>>> On Mon, Sep 12, 2016 at 1:48 PM, haosdent <haosd...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi, @victor What's your health check agent used for? Because Mesos
>>>>>>> supports health checks now.
>>>>>>>
>>>>>>> On Tue, Sep 13, 2016 at 1:46 AM, Victor L <vlyamt...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> I am writing "healthcheck agent" for mesos deployment framework as
>>>>>>>> independent thread periodically checking if main process ( started by
>>>>>>>> framework) is running...
>>>>>>>> What would be the mechanism to "communicate" failure to the
>>>>>>>> framework  to cause specific outcome? For example: how can i use 
>>>>>>>> failure to
>>>>>>>> cause framework to reschedule deployment on different node?
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Haosdent Huang
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Haosdent Huang
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Reply via email to