mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Hegner (JIRA)" <>
Subject [jira] [Created] (MESOS-5294) Status updates after a health check and incomplete
Date Wed, 27 Apr 2016 19:54:13 GMT
Travis Hegner created MESOS-5294:

             Summary: Status updates after a health check and incomplete
                 Key: MESOS-5294
             Project: Mesos
          Issue Type: Bug
         Environment: mesos 0.28.0, docker 1.11, marathon 0.15.3, mesos-dns, ubuntu 14.04
            Reporter: Travis Hegner
            Assignee: Travis Hegner

With command health checks enabled via marathon, mesos-dns will resolve the task correctly
until the task is reported as "healthy". At that point, mesos-dns stops resolving the task

Digging through src/docker/executor.cpp, I found that in the "taskHealthUpdated()" function
is attempting to copy the taskID to the new status instance with "status.mutable_task_id()->CopyFrom(taskID);",
but other instances of status updates have a similar line "status.mutable_task_id()->CopyFrom(taskID.get());".

My assumption is that this difference is causing the status update after a health check to
not have a proper taskID, which in turn is causing an incorrect state.json output.

I'll try to get a patch together soon.

This message was sent by Atlassian JIRA

View raw message