mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pradeep Chhetri <pradeep.chhetr...@gmail.com>
Subject Re: Question regarding docker containerizer
Date Sat, 27 Feb 2016 13:01:18 GMT
Thank you Guangya, that perfectly answers my doubt.

On Sat, Feb 27, 2016 at 8:15 AM, Guangya Liu <gyliu513@gmail.com> wrote:

> The Docker Executor was also managed by Mesos itself, you can refer to
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L1197
> , the executor was managed by mesos and mesos can set the default resources
> for the executor:
> https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3732-L3742
>
> And the default resources for executor cpus(*):0.1; mem(*):32, so you will
> not get any warning message.
>
> Thanks,
>
> Guangya
>
> On Fri, Feb 26, 2016 at 6:08 PM, Pradeep Chhetri <
> pradeep.chhetri89@gmail.com> wrote:
>
>> Actually the reason i asked this question is because i am unable to
>> generate these warning messages by setting MEMORY < MIN_MEM and CPU <
>> MIN_CPUS in case of docker containers started using marathon.
>>
>>
>> https://github.com/apache/mesos/blob/4d4d7166414f0ebd8d5e40df34070446098a3c91/src/master/validation.cpp#L397-L425
>>
>> So i was trying to figure out whether
>>
>>
>> https://github.com/apache/mesos/blob/4d4d7166414f0ebd8d5e40df34070446098a3c91/src/master/validation.cpp#L399
>> is resulting in true or false in case of docker containers started using
>> marathon.
>>
>>
>> On Fri, Feb 26, 2016 at 8:20 AM, Pradeep Chhetri <
>> pradeep.chhetri89@gmail.com> wrote:
>>
>>> Thank you Jie and Jojy for the help.
>>>
>>> On Fri, Feb 26, 2016 at 4:50 AM, Jojy Varghese <jojy@mesosphere.io>
>>> wrote:
>>>
>>>> Hi Pradeep,
>>>>
>>>> The relevant code if you are interested is at :
>>>>
>>>> https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3561
>>>>
>>>> https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3672
>>>>
>>>> -jojy
>>>>
>>>>
>>>> On Feb 25, 2016, at 4:10 PM, Pradeep Chhetri <
>>>> pradeep.chhetri89@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.jay@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.chhetri89@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.jay@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.chhetri89@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...
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Pradeep Chhetri
>>>
>>> In the world of Linux, who needs Windows and Gates...
>>>
>>
>>
>>
>> --
>> Pradeep Chhetri
>>
>> In the world of Linux, who needs Windows and Gates...
>>
>
>


-- 
Pradeep Chhetri

In the world of Linux, who needs Windows and Gates...

Mime
View raw message