Venkat,
There should be some information in the master logs to help you debug. In
the case of a successful status update, you will see something like the
following:

master.cpp:5848] Status update TASK_RUNNING (UUID:
ccb9beae-d62c-40f1-9d4e-9b6153cb0fff) for task test-task of framework
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-0002 from agent
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-S0 at slave(1)@127.0.0.1:5051
(localhost)
master.cpp:5910] Forwarding status update TASK_RUNNING (UUID:
ccb9beae-d62c-40f1-9d4e-9b6153cb0fff) for task test-task of framework
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-0002
master.cpp:7953] Updating the state of task test-task of framework
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-0002 (latest state: TASK_RUNNING,
status update state: TASK_RUNNING)
master.cpp:4950] Processing ACKNOWLEDGE call
ccb9beae-d62c-40f1-9d4e-9b6153cb0fff for task test-task of framework
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-0002 (mesos-execute instance) on agent
8fffa9d5-bb6e-4af1-8a4a-4f5fce36df6b-S0

Looking for these lines could help you discover where the issue is; i.e.,
if the status update is being sent but not received, or if it is not being
sent to the framework at all.

Cheers,
Greg

On Wed, Jan 11, 2017 at 11:44 AM, Venkat Morampudi <
venkatmoramp...@gmail.com> wrote:

> Hi,
>
> I am facing an issue with my Mesos framework with status updates.
> Randomly, Task Status messages doesn’t reach to the Framework scheduler.
> When this happens Offer declines doesn’t take affect. After sometime thing
> seem to be getting to normal. Looks like timeout is being triggered. I
> couldn’t find anything anything obvious from the log files. I would really
> appreciate if you can help me with this.
>
> Thanks,
> Venkat

Reply via email to