Thanks @haosdent, let me try it. 2016-11-21 14:33 GMT+08:00 haosdent <[email protected]>:
> 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 <[email protected]> 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 <[email protected]> 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] <defunct> >>> root 14505 19464 0 Oct25 ? 00:00:00 [docker] <defunct> >>> root 16069 19464 0 Oct25 ? 00:00:00 [docker] <defunct> >>> root 19962 19464 0 Oct25 ? 00:00:00 [docker] <defunct> >>> root 23346 19464 0 Oct25 ? 00:00:00 [docker] <defunct> >>> root 24544 19464 0 Oct25 ? 00:00:00 [docker] <defunct> >>> ``` >>> >>> 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 >
