Yeah, that's the command task. Mesos run all tasks using some executor. If
the user does not specify one (command task case), we will use the default
mesos executor.

On Thu, Feb 25, 2016 at 4:10 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hi Jie,
>
> I see executor_id as empty. Does this means that it is running as task and
> there is no executor for it ? Although, in the ps output, I see mesos-slave
> is spawning a mesos-docker-executor which in turn spawning the docker
> command. Here is the detail of one of the marathon task:
>
> {"id": "logs_role_kibana.3b024b6e-dbf3-11e5-bc67-56847afe9799","name": "
> kibana.role.logs","framework_id": "
> 20150904-093718-2198675372-5050-22379-0000","executor_id": "","slave_id":
> "a4f30c35-eee7-4110-a82f-cab5522c9b1b-S4","state": "TASK_RUNNING","
> resources": {"cpus": 0.5,"disk": 0,"mem": 1024,"ports": "[31050-31050]"},"
> statuses": [{"state": "TASK_RUNNING","timestamp": 1456427344.63661,"labels
> ": [{"key": "Docker.NetworkSettings.IPAddress","value": "172.17.0.11"}],"
> container_status": {"network_infos": [{"ip_address": "172.17.0.11","
> ip_addresses": [{"ip_address": "172.17.0.11"}]}]}}],"container": {"type":
> "DOCKER","docker": {"image": "kibana:4.3.1","network": "BRIDGE","
> port_mappings": [{"host_port": 31050,"container_port": 5601,"protocol": "
> tcp"}],"privileged": false,"parameters": [{"key": "publish-all","value": "
> true"}],"force_pull_image": true}}},
>
>
>
> On Thu, Feb 25, 2016 at 11:59 PM, Jie Yu <yujie....@gmail.com> wrote:
>
>> You can checkout the state.json endpoint on the master
>>
>> On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri <
>> pradeep.chhetr...@gmail.com> wrote:
>>
>>> Hello Jie,
>>>
>>> Thank you for the quick reply. Sorry for asking silly question. How can
>>> i look for the taskinfo of a running container ? Can i see the TaskInfo
>>> details in the mesos master UI for a task?
>>>
>>> On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu <yujie....@gmail.com> wrote:
>>>
>>>> You can take a look at the TaskInfo. If the TaskInfo does not have
>>>> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
>>>> executor and send the task to the executor.
>>>>
>>>> - Jie
>>>>
>>>> On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
>>>> pradeep.chhetr...@gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> From docker containerizer documentation (
>>>>> http://mesos.apache.org/documentation/latest/docker-containerizer/),
>>>>>
>>>>> *"Users can either launch a Docker image as a Task, or as an
>>>>> Executor."*
>>>>>
>>>>> How can i identify whether a docker container started by lets say
>>>>> marathon is running as a task or as an executor ?
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>> -Pradeep
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Pradeep Chhetri
>>>
>>> In the world of Linux, who needs Windows and Gates...
>>>
>>
>>
>
>
> --
> Pradeep Chhetri
>
> In the world of Linux, who needs Windows and Gates...
>

Reply via email to