Re: Path vs Mount disk resources

[Jie Yu]

>
> The documentation states "non performance-critical applications" and
> "should only be done in a testing or staging environment" about Path type
> resources. Is there any particular reason for that?


I think the documentation is not very precise. Path disk resource is the
default disk resource, and has been used in prod for years for task's logs
and other stuffs in its sandbox.

MOUNT disk was introduced mainly for data services which may require disk
performance isolation and wants to have exclusive access to a disk.

Both of them are definitely ready for production.

- Jie

On Mon, Nov 21, 2016 at 9:48 AM, Tobias Pfeiffer  wrote:

> Hi,
>
> I have a Mesos cluster where each node has both SSD and HDD disks, so I
> want to offer them separately as described in http://mesos.apache.org/
> documentation/latest/multiple-disk/
>
> I am not sure yet where the OS will be installed, but I guess on the disk
> that holds the OS I cannot use a Mount type resource, but would have to use
> a Path type resource? The documentation states "non performance-critical
> applications" and "should only be done in a testing or staging environment"
> about Path type resources. Is there any particular reason for that?
>
> I imagine if I have something like, say,
>
>   /  HDD, 1000 GB
>   /mnt/data  SSD, 200 GB
>
> would it make sense to configure the disk resources like
>
> {
>   "resources" : [
> {
>   "name" : "disk",
>   "type" : "SCALAR",
>   "scalar" : { "value" : 80 },
>   "disk" : {
> "source" : {
>   "type" : "PATH",
>   "path" : { "root" : "/var/lib/mesos-data" }
> }
>   }
> },
> {
>   "name" : "disk",
>   "type" : "SCALAR",
>   "scalar" : { "value" : 20 },
>   "disk" : {
> "source" : {
>   "type" : "MOUNT",
>   "mount" : { "root" : "/mnt/data" }
> }
>   }
> }
>   ]
> }
>
> or is that something that's not suitable for production?
>
> Thanks,
> Tobias
>
>

Re: Running mesos-slave in the docker that leave many zombie process

[X Brick]

Thanks @haosdent, let me try it.

2016-11-21 14:33 GMT+08:00 haosdent :

> Pass the `--pid=host` flag when starting the docker container  may resolve
> this.
> >start the mesos_slave container with "--pid=host" so that it uses the
> process namespace of the host.
>
> On Mon, Nov 21, 2016 at 2:30 PM, haosdent  wrote:
>
>> No sure if it related to this issue https://github.com/mesos
>> phere/docker-containers/issues/9
>>
>> On Mon, Nov 21, 2016 at 12:27 PM, X Brick  wrote:
>>
>>> Hi,
>>>
>>> I meet a problem when running mesos-slave in the docker. Here are some
>>> zombie process in this way.
>>>
>>> ```
>>> root 10547 19464  0 Oct25 ?00:00:00 [docker] 
>>> root 14505 19464  0 Oct25 ?00:00:00 [docker] 
>>> root 16069 19464  0 Oct25 ?00:00:00 [docker] 
>>> root 19962 19464  0 Oct25 ?00:00:00 [docker] 
>>> root 23346 19464  0 Oct25 ?00:00:00 [docker] 
>>> root 24544 19464  0 Oct25 ?00:00:00 [docker] 
>>> ```
>>>
>>> And I find the zombies come from mesos-slave process:
>>>
>>> ```
>>> pstree -p -s 10547
>>> systemd(1)───docker-containe(19448)───mesos-slave(19464)───docker(10547)
>>> ```
>>>
>>> The logs has been deleted by the cron job a few weeks ago, but I
>>> remember so many `Failed to shutdown socket with fd xx: Transport
>>> endpoint is not connected` in the log.
>>>
>>> I report this to the JIRA: https://issues.apache.org/jira
>>> /browse/MESOS-6615
>>>
>>> Is there anyone saw this issue before ?
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Running mesos-slave in the docker that leave many zombie process

[haosdent]

Pass the `--pid=host` flag when starting the docker container  may resolve
this.
>start the mesos_slave container with "--pid=host" so that it uses the
process namespace of the host.

On Mon, Nov 21, 2016 at 2:30 PM, haosdent  wrote:

> No sure if it related to this issue https://github.com/
> mesosphere/docker-containers/issues/9
>
> On Mon, Nov 21, 2016 at 12:27 PM, X Brick  wrote:
>
>> Hi,
>>
>> I meet a problem when running mesos-slave in the docker. Here are some
>> zombie process in this way.
>>
>> ```
>> root 10547 19464  0 Oct25 ?00:00:00 [docker] 
>> root 14505 19464  0 Oct25 ?00:00:00 [docker] 
>> root 16069 19464  0 Oct25 ?00:00:00 [docker] 
>> root 19962 19464  0 Oct25 ?00:00:00 [docker] 
>> root 23346 19464  0 Oct25 ?00:00:00 [docker] 
>> root 24544 19464  0 Oct25 ?00:00:00 [docker] 
>> ```
>>
>> And I find the zombies come from mesos-slave process:
>>
>> ```
>> pstree -p -s 10547
>> systemd(1)───docker-containe(19448)───mesos-slave(19464)───docker(10547)
>> ```
>>
>> The logs has been deleted by the cron job a few weeks ago, but I remember
>> so many `Failed to shutdown socket with fd xx: Transport endpoint is not
>> connected` in the log.
>>
>> I report this to the JIRA: https://issues.apache.org/jira
>> /browse/MESOS-6615
>>
>> Is there anyone saw this issue before ?
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
Best Regards,
Haosdent Huang

Running mesos-slave in the docker that leave many zombie process

[X Brick]

Hi,

I meet a problem when running mesos-slave in the docker. Here are some
zombie process in this way.

```
root 10547 19464  0 Oct25 ?00:00:00 [docker] 
root 14505 19464  0 Oct25 ?00:00:00 [docker] 
root 16069 19464  0 Oct25 ?00:00:00 [docker] 
root 19962 19464  0 Oct25 ?00:00:00 [docker] 
root 23346 19464  0 Oct25 ?00:00:00 [docker] 
root 24544 19464  0 Oct25 ?00:00:00 [docker] 
```

And I find the zombies come from mesos-slave process:

```
pstree -p -s 10547
systemd(1)───docker-containe(19448)───mesos-slave(19464)───docker(10547)
```

The logs has been deleted by the cron job a few weeks ago, but I remember
so many `Failed to shutdown socket with fd xx: Transport endpoint is not
connected` in the log.

I report this to the JIRA: https://issues.apache.org/jira/browse/MESOS-6615

Is there anyone saw this issue before ?