[jira] [Commented] (MESOS-9027) GPU Isolator still depends on cgroups/devices agent flag given cgrous/all is supported.

[ https://issues.apache.org/jira/browse/MESOS-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523763#comment-16523763 ] Qian Zhang commented on MESOS-9027: --- RR: [https://reviews.apache.org/r/67743/]  > GPU Isolator still

[jira] [Assigned] (MESOS-9027) GPU Isolator still depends on cgroups/devices agent flag given cgrous/all is supported.

[ https://issues.apache.org/jira/browse/MESOS-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang reassigned MESOS-9027: - Assignee: Qian Zhang > GPU Isolator still depends on cgroups/devices agent flag given

[jira] [Commented] (MESOS-9025) The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent

[ https://issues.apache.org/jira/browse/MESOS-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523097#comment-16523097 ] Qian Zhang commented on MESOS-9025: --- RR: https://reviews.apache.org/r/67728/ > The container which

[jira] [Assigned] (MESOS-9025) The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent

[ https://issues.apache.org/jira/browse/MESOS-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang reassigned MESOS-9025: - Assignee: Jie Yu > The container which joins CNI network and has checkpoint enabled will be >

[jira] [Commented] (MESOS-9025) The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent

[ https://issues.apache.org/jira/browse/MESOS-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521358#comment-16521358 ] Qian Zhang commented on MESOS-9025: --- It seems this bug was introduced by this patch:

[jira] [Created] (MESOS-9025) The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent

Qian Zhang created MESOS-9025: - Summary: The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent Key: MESOS-9025 URL: https://issues.apache.org/jira/browse/MESOS-9025

[jira] [Comment Edited] (MESOS-9025) The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent

[ https://issues.apache.org/jira/browse/MESOS-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521358#comment-16521358 ] Qian Zhang edited comment on MESOS-9025 at 6/25/18 12:31 AM: - It seems this

[jira] [Comment Edited] (MESOS-8327) Add container-specific CGroup FS mounts under /sys/fs/cgroup/* to Mesos containers

[ https://issues.apache.org/jira/browse/MESOS-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510548#comment-16510548 ] Qian Zhang edited comment on MESOS-8327 at 6/20/18 2:56 AM: RR: 

[jira] [Assigned] (MESOS-9031) Mesos CNI portmap plugins' iptables rules doesn't allow connections via host ip and port from the same bridge container network

[ https://issues.apache.org/jira/browse/MESOS-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang reassigned MESOS-9031: - Assignee: Qian Zhang Sprint: Mesosphere Sprint 2018-23 > Mesos CNI portmap plugins'

[jira] [Commented] (MESOS-9039) CNI isolator recovery should wait until unknown orphan cleanup is done

[ https://issues.apache.org/jira/browse/MESOS-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530649#comment-16530649 ] Qian Zhang commented on MESOS-9039: --- The main purpose of this fix is to ensure the test

[jira] [Commented] (MESOS-9031) Mesos CNI portmap plugins' iptables rules doesn't allow connections via host ip and port from the same bridge container network

[ https://issues.apache.org/jira/browse/MESOS-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530120#comment-16530120 ] Qian Zhang commented on MESOS-9031: --- [~Kirill P] So there are two service nodes (i.e., two Mesos tasks)

[jira] [Commented] (MESOS-9031) Mesos CNI portmap plugins' iptables rules doesn't allow connections via host ip and port from the same bridge container network

[ https://issues.apache.org/jira/browse/MESOS-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530038#comment-16530038 ] Qian Zhang commented on MESOS-9031: --- [~Kirill P] For the two tasks, do they have port mapping enabled

[jira] [Created] (MESOS-8876) Normal exit of Docker container using rexray volume results in TASK_FAILED

Qian Zhang created MESOS-8876: - Summary: Normal exit of Docker container using rexray volume results in TASK_FAILED Key: MESOS-8876 URL: https://issues.apache.org/jira/browse/MESOS-8876 Project: Mesos

[jira] [Created] (MESOS-8877) Docker container's resources will be wrongly enlarged in cgroups after agent recovery

Qian Zhang created MESOS-8877: - Summary: Docker container's resources will be wrongly enlarged in cgroups after agent recovery Key: MESOS-8877 URL: https://issues.apache.org/jira/browse/MESOS-8877

[jira] [Comment Edited] (MESOS-8809) Add functions for manipulating POSIX ACLs into stout

[ https://issues.apache.org/jira/browse/MESOS-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454262#comment-16454262 ] Qian Zhang edited comment on MESOS-8809 at 4/27/18 1:36 AM: RR: 

[jira] [Commented] (MESOS-8834) libprocess底层internal::send和internal::_send相互调用， 当outgoing[socket]里一直有数据包要发送时，那么存在栈耗尽 core dump问题

[ https://issues.apache.org/jira/browse/MESOS-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455602#comment-16455602 ] Qian Zhang commented on MESOS-8834: --- [~bennoe] You are right, it is same as  MESOS-8594, so I have

[jira] [Comment Edited] (MESOS-8877) Docker container's resources will be wrongly enlarged in cgroups after agent recovery

[ https://issues.apache.org/jira/browse/MESOS-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462217#comment-16462217 ] Qian Zhang edited comment on MESOS-8877 at 5/3/18 9:54 AM: --- The root cause of

[jira] [Commented] (MESOS-8877) Docker container's resources will be wrongly enlarged in cgroups after agent recovery

[ https://issues.apache.org/jira/browse/MESOS-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462217#comment-16462217 ] Qian Zhang commented on MESOS-8877: --- The root cause of this issue, when we recover a container in

[jira] [Commented] (MESOS-7509) CniIsolatorPortMapperTest.ROOT_INTERNET_CURL_PortMapper fails on some Linux distros.

[ https://issues.apache.org/jira/browse/MESOS-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211060#comment-16211060 ] Qian Zhang commented on MESOS-7509: --- For the test {{ROOT_INTERNET_CURL_PortMapper}}, the root cause that

[jira] [Commented] (MESOS-9031) Mesos CNI portmap plugins' iptables rules doesn't allow connections via host ip and port from the same bridge container network

[ https://issues.apache.org/jira/browse/MESOS-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531432#comment-16531432 ] Qian Zhang commented on MESOS-9031: --- [~Kirill P] I reproduced this issue with the following steps: #

[jira] [Updated] (MESOS-7488) Add `--ip6` and `--ip6_discovery_command` flag to Mesos agent

[ https://issues.apache.org/jira/browse/MESOS-7488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-7488: -- Description: As a first step to support IPv6 containers on Mesos, we need to provide {{--ip6}} and

[jira] [Created] (MESOS-8432) Introduce a unified artifact store

Qian Zhang created MESOS-8432: - Summary: Introduce a unified artifact store Key: MESOS-8432 URL: https://issues.apache.org/jira/browse/MESOS-8432 Project: Mesos Issue Type: Epic

[jira] [Created] (MESOS-8433) Design doc for unified artifact store

Qian Zhang created MESOS-8433: - Summary: Design doc for unified artifact store Key: MESOS-8433 URL: https://issues.apache.org/jira/browse/MESOS-8433 Project: Mesos Issue Type: Task

[jira] [Assigned] (MESOS-8433) Design doc for unified artifact store

[ https://issues.apache.org/jira/browse/MESOS-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang reassigned MESOS-8433: - Assignee: Qian Zhang > Design doc for unified artifact store >

[jira] [Assigned] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang reassigned MESOS-8279: - Assignee: Qian Zhang > Persistent volumes are not visible in Mesos UI using default executor on

[jira] [Updated] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-8279: -- Sprint: Mesosphere Sprint 72 > Persistent volumes are not visible in Mesos UI using default executor on

[jira] [Commented] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317514#comment-16317514 ] Qian Zhang commented on MESOS-8279: --- [~vinodkone] proposed a solution: calling {{Files::attach()}} to

[jira] [Commented] (MESOS-8305) DefaultExecutorTest.ROOT_MultiTaskgroupSharePidNamespace is flaky.

[ https://issues.apache.org/jira/browse/MESOS-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330594#comment-16330594 ] Qian Zhang commented on MESOS-8305: --- >From the log, we can see the pid namespace we read for the second

[jira] [Updated] (MESOS-8305) DefaultExecutorTest.ROOT_MultiTaskgroupSharePidNamespace is flaky.

[ https://issues.apache.org/jira/browse/MESOS-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-8305: -- Story Points: 2 Sprint: Mesosphere Sprint 72 >

[jira] [Updated] (MESOS-8444) Agent miss to detach virtual paths for the executor's sandbox

[ https://issues.apache.org/jira/browse/MESOS-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-8444: -- Description: I launched a task via {{mesos-execute}} which just did a {{sleep 10}}, when the task

[jira] [Updated] (MESOS-8444) Agent miss to detach virtual paths for the executor's sandbox

[ https://issues.apache.org/jira/browse/MESOS-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-8444: -- Description: I launched a task group which has one task via {{mesos-execute}}, and that task just did

[jira] [Created] (MESOS-8444) Agent miss to detach virtual paths for the executor's sandbox

Qian Zhang created MESOS-8444: - Summary: Agent miss to detach virtual paths for the executor's sandbox Key: MESOS-8444 URL: https://issues.apache.org/jira/browse/MESOS-8444 Project: Mesos Issue

[jira] [Commented] (MESOS-8444) Agent miss to detach virtual paths for the executor's sandbox

[ https://issues.apache.org/jira/browse/MESOS-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325602#comment-16325602 ] Qian Zhang commented on MESOS-8444: --- RR: https://reviews.apache.org/r/65156/ > Agent miss to detach

[jira] [Created] (MESOS-8446) Agent miss to detach `virtualLatestPath` for the executor's sandbox during recovery

Qian Zhang created MESOS-8446: - Summary: Agent miss to detach `virtualLatestPath` for the executor's sandbox during recovery Key: MESOS-8446 URL: https://issues.apache.org/jira/browse/MESOS-8446 Project:

[jira] [Updated] (MESOS-8444) GC failure causes agent miss to detach virtual paths for the executor's sandbox

[ https://issues.apache.org/jira/browse/MESOS-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-8444: -- Summary: GC failure causes agent miss to detach virtual paths for the executor's sandbox (was: Agent

[jira] [Commented] (MESOS-8446) Agent miss to detach `virtualLatestPath` for the executor's sandbox during recovery

[ https://issues.apache.org/jira/browse/MESOS-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326250#comment-16326250 ] Qian Zhang commented on MESOS-8446: --- RR: https://reviews.apache.org/r/65167/ > Agent miss to detach

[jira] [Commented] (MESOS-6822) CNI reports confusing error message for failed interface setup.

[ https://issues.apache.org/jira/browse/MESOS-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335568#comment-16335568 ] Qian Zhang commented on MESOS-6822: --- The way we checked the return value of {{os::spawn}} is not

[jira] [Updated] (MESOS-6822) CNI reports confusing error message for failed interface setup.

[ https://issues.apache.org/jira/browse/MESOS-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Zhang updated MESOS-6822: -- Shepherd: Jie Yu Story Points: 2 Sprint: Mesosphere Sprint 73 Target

[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang commented on MESOS-8125: --- {quote}Also looks like docker containerizer doesn't recover the

[jira] [Commented] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328209#comment-16328209 ] Qian Zhang commented on MESOS-8279: --- commit 9585a2173970589f91858301c66479827c1370a9 Author: Qian Zhang

[jira] [Commented] (MESOS-8444) GC failure causes agent miss to detach virtual paths for the executor's sandbox

[ https://issues.apache.org/jira/browse/MESOS-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328216#comment-16328216 ] Qian Zhang commented on MESOS-8444: --- commit 5225a49c495bc7e3362bcee2d460d8c99111c7f4 Author: Qian Zhang

[jira] [Commented] (MESOS-8446) Agent miss to detach `virtualLatestPath` for the executor's sandbox during recovery

[ https://issues.apache.org/jira/browse/MESOS-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328204#comment-16328204 ] Qian Zhang commented on MESOS-8446: --- commit 2c5da1b668de91e33831caafb18a3b4d71b26c69 Author: Qian Zhang

[jira] [Commented] (MESOS-6822) CNI reports confusing error message for failed interface setup.

[ https://issues.apache.org/jira/browse/MESOS-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338509#comment-16338509 ] Qian Zhang commented on MESOS-6822: --- commit 2cdbec02e37c794627204f0e1fadf09e5325507d Author: Qian Zhang

[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345186#comment-16345186 ] Qian Zhang commented on MESOS-8125: --- Had a discussion with [~vinodkone], basically we should not allow

[jira] [Commented] (MESOS-8509) Launching a Docker container with `--restart=always` may cause the Docker container is running after the task completes

[ https://issues.apache.org/jira/browse/MESOS-8509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345176#comment-16345176 ] Qian Zhang commented on MESOS-8509: --- Basically we should add a validation to disallow setting Docker

[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345240#comment-16345240 ] Qian Zhang commented on MESOS-8125: --- I have another proposal: In `DockerContainerizerProcess::_recover`,

[jira] [Created] (MESOS-8509) Launching a Docker container with `--restart=always` may cause the Docker container is running after the task completes

Qian Zhang created MESOS-8509: - Summary: Launching a Docker container with `--restart=always` may cause the Docker container is running after the task completes Key: MESOS-8509 URL:

[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346111#comment-16346111 ] Qian Zhang commented on MESOS-8125: --- commit b6da63ba2a318e911944a3c475ecf472b1ca86e0 Author: Qian Zhang

[jira] [Created] (MESOS-8515) Docker containerizer does not recover the executor pid

Qian Zhang created MESOS-8515: - Summary: Docker containerizer does not recover the executor pid Key: MESOS-8515 URL: https://issues.apache.org/jira/browse/MESOS-8515 Project: Mesos Issue Type:

[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346167#comment-16346167 ] Qian Zhang commented on MESOS-8125: --- For the issue that Docker containerizer does not recover the

[jira] [Commented] (MESOS-8515) Docker containerizer does not recover the executor pid

[ https://issues.apache.org/jira/browse/MESOS-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346199#comment-16346199 ] Qian Zhang commented on MESOS-8515: --- As a fix, we can set the executor pid for the container in

[jira] [Commented] (MESOS-8488) Docker bug can cause unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346900#comment-16346900 ] Qian Zhang commented on MESOS-8488: --- I think both of the two solutions mentioned in the description have

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:46 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:47 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:48 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:48 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:49 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:45 AM: {quote}Also looks

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/29/18 6:44 AM: {quote}Also looks

[jira] [Created] (MESOS-8502) The test `DefaultExecutorTest.KillTaskGroupOnTaskFailure` is flaky

Qian Zhang created MESOS-8502: - Summary: The test `DefaultExecutorTest.KillTaskGroupOnTaskFailure` is flaky Key: MESOS-8502 URL: https://issues.apache.org/jira/browse/MESOS-8502 Project: Mesos

[jira] [Comment Edited] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341146#comment-16341146 ] Qian Zhang edited comment on MESOS-8125 at 1/28/18 7:16 AM: {quote}Also looks

[jira] [Commented] (MESOS-7605) UCR doesn't isolate uts namespace w/ host networking

[ https://issues.apache.org/jira/browse/MESOS-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348224#comment-16348224 ] Qian Zhang commented on MESOS-7605: --- [~jamespeach] I reviewed your patches and have a comment: When UTS

[jira] [Comment Edited] (MESOS-7605) UCR doesn't isolate uts namespace w/ host networking

[ https://issues.apache.org/jira/browse/MESOS-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348224#comment-16348224 ] Qian Zhang edited comment on MESOS-7605 at 2/1/18 8:51 AM: --- [~jamespeach] I

[jira] [Created] (MESOS-8565) Persistent volumes are not visible in Mesos UI when launching a pod in DC/OS

Qian Zhang created MESOS-8565: - Summary: Persistent volumes are not visible in Mesos UI when launching a pod in DC/OS Key: MESOS-8565 URL: https://issues.apache.org/jira/browse/MESOS-8565 Project: Mesos

[jira] [Commented] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359152#comment-16359152 ] Qian Zhang commented on MESOS-8279: --- For the second case mentioned in my previous comment, I have

[jira] [Commented] (MESOS-8565) Persistent volumes are not visible in Mesos UI when launching a pod in DC/OS

[ https://issues.apache.org/jira/browse/MESOS-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359162#comment-16359162 ] Qian Zhang commented on MESOS-8565: --- The root cause of this issue is, when user uses DC/OS (actually

[jira] [Comment Edited] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356942#comment-16356942 ] Qian Zhang edited comment on MESOS-8279 at 2/13/18 7:24 AM: The above fix can

[jira] [Commented] (MESOS-8488) Docker bug can cause unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363428#comment-16363428 ] Qian Zhang commented on MESOS-8488: --- commit a7714536fad1140fd0c07c47e32b40e9ed00a3c3 Author: Qian Zhang

[jira] [Commented] (MESOS-8468) `LAUNCH_GROUP` failure tears down the default executor.

[ https://issues.apache.org/jira/browse/MESOS-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363883#comment-16363883 ] Qian Zhang commented on MESOS-8468: --- https://reviews.apache.org/r/65616/ > `LAUNCH_GROUP` failure tears

[jira] [Commented] (MESOS-8468) `LAUNCH_GROUP` failure tears down the default executor.

[ https://issues.apache.org/jira/browse/MESOS-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363885#comment-16363885 ] Qian Zhang commented on MESOS-8468: --- commit 632ff7f7f8e32d3f9507e9199c8a253ff755224e Author: Gaston

[jira] [Commented] (MESOS-8565) Persistent volumes are not visible in Mesos UI when launching a pod in DC/OS

[ https://issues.apache.org/jira/browse/MESOS-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359452#comment-16359452 ] Qian Zhang commented on MESOS-8565: --- RR: https://reviews.apache.org/r/65570/ > Persistent volumes are

[jira] [Commented] (MESOS-8488) Docker bug can cause unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353568#comment-16353568 ] Qian Zhang commented on MESOS-8488: --- [~greggomann], I had a discussion with [~vinodkone], he suggests we

[jira] [Commented] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356942#comment-16356942 ] Qian Zhang commented on MESOS-8279: --- The above fix can handle this case: Framework launches a task group 

[jira] [Comment Edited] (MESOS-8279) Persistent volumes are not visible in Mesos UI using default executor on Linux.

[ https://issues.apache.org/jira/browse/MESOS-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356942#comment-16356942 ] Qian Zhang edited comment on MESOS-8279 at 2/8/18 1:49 PM: --- The above fix can

[jira] [Commented] (MESOS-8502) The test `DefaultExecutorTest.KillTaskGroupOnTaskFailure` is flaky

[ https://issues.apache.org/jira/browse/MESOS-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355163#comment-16355163 ] Qian Zhang commented on MESOS-8502: --- >From the attached log, I can see agent has received the

[jira] [Commented] (MESOS-8534) Allow nested containers in TaskGroups to have separate network namespaces

[ https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373762#comment-16373762 ] Qian Zhang commented on MESOS-8534: --- [~sagar8192] for the use case that you mentioned in the

[jira] [Commented] (MESOS-7176) Add versioning support to network/cni isolator

[ https://issues.apache.org/jira/browse/MESOS-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374228#comment-16374228 ] Qian Zhang commented on MESOS-7176: --- According to [CNI

[jira] [Commented] (MESOS-8812) Grant non-root task user the permissions to access the DOCKER_VOLUME volume

[ https://issues.apache.org/jira/browse/MESOS-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563303#comment-16563303 ] Qian Zhang commented on MESOS-8812: --- RR: https://reviews.apache.org/r/68125/ > Grant non-root task

[jira] [Commented] (MESOS-8813) Make multiple tasks with different users can access a shared persistent volume

[ https://issues.apache.org/jira/browse/MESOS-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566530#comment-16566530 ] Qian Zhang commented on MESOS-8813: --- RR: https://reviews.apache.org/r/68161/ > Make multiple tasks

[jira] [Commented] (MESOS-8811) Grant non-root task user the permissions to access the image volume

[ https://issues.apache.org/jira/browse/MESOS-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555780#comment-16555780 ] Qian Zhang commented on MESOS-8811: --- RR: https://reviews.apache.org/r/68040/ > Grant non-root task

[jira] [Comment Edited] (MESOS-8814) Mount the volume based on `Volume.mode`

[ https://issues.apache.org/jira/browse/MESOS-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569023#comment-16569023 ] Qian Zhang edited comment on MESOS-8814 at 8/6/18 7:56 AM: --- RR: 

[jira] [Comment Edited] (MESOS-9031) Mesos CNI portmap plugins' iptables rules doesn't allow connections via host ip and port from the same bridge container network

[ https://issues.apache.org/jira/browse/MESOS-9031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537867#comment-16537867 ] Qian Zhang edited comment on MESOS-9031 at 8/7/18 12:03 AM: For the issues

[jira] [Commented] (MESOS-8814) Mount the volume based on `Volume.mode`

[ https://issues.apache.org/jira/browse/MESOS-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569023#comment-16569023 ] Qian Zhang commented on MESOS-8814: --- RR: [https://reviews.apache.org/r/68203/] > Mount the volume

[jira] [Commented] (MESOS-9131) Health checks launching nested containers while a container is being destroyed lead to unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586013#comment-16586013 ] Qian Zhang commented on MESOS-9131: --- The root cause of this issue is, the I/O switchboard server

[jira] [Comment Edited] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591103#comment-16591103 ] Qian Zhang edited comment on MESOS-8568 at 8/24/18 3:20 AM: [~vinodkone]

[jira] [Commented] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591106#comment-16591106 ] Qian Zhang commented on MESOS-8568: --- RR: https://reviews.apache.org/r/68495/ > Command checks should

[jira] [Commented] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591103#comment-16591103 ] Qian Zhang commented on MESOS-8568: --- [~vinodkone] Yeah, I noticed that as well. When the I/O

[jira] [Commented] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591235#comment-16591235 ] Qian Zhang commented on MESOS-8568: --- I ran the exactly same reproduce steps with the above patch

[jira] [Comment Edited] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591235#comment-16591235 ] Qian Zhang edited comment on MESOS-8568 at 8/24/18 7:05 AM: I ran the exactly

[jira] [Comment Edited] (MESOS-9131) Health checks launching nested containers while a container is being destroyed lead to unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585328#comment-16585328 ] Qian Zhang edited comment on MESOS-9131 at 8/20/18 1:50 AM: I found a way to

[jira] [Comment Edited] (MESOS-9131) Health checks launching nested containers while a container is being destroyed lead to unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585328#comment-16585328 ] Qian Zhang edited comment on MESOS-9131 at 8/20/18 1:36 AM: I found a way to

[jira] [Commented] (MESOS-9131) Health checks launching nested containers while a container is being destroyed lead to unkillable tasks

[ https://issues.apache.org/jira/browse/MESOS-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585328#comment-16585328 ] Qian Zhang commented on MESOS-9131: --- I found a way to steadily reproduce this issue: 1. Start Mesos

[jira] [Comment Edited] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588976#comment-16588976 ] Qian Zhang edited comment on MESOS-8568 at 8/22/18 2:56 PM: Reproduce steps:

[jira] [Comment Edited] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588976#comment-16588976 ] Qian Zhang edited comment on MESOS-8568 at 8/22/18 3:02 PM: Reproduce steps:

[jira] [Commented] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588976#comment-16588976 ] Qian Zhang commented on MESOS-8568: --- Reproduce steps: 1. To simulate the failure of launching nested

[jira] [Comment Edited] (MESOS-8568) Command checks should always call `WAIT_NESTED_CONTAINER` before `REMOVE_NESTED_CONTAINER`

[ https://issues.apache.org/jira/browse/MESOS-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588976#comment-16588976 ] Qian Zhang edited comment on MESOS-8568 at 8/22/18 3:01 PM: Reproduce steps:

[jira] [Commented] (MESOS-8810) Grant non-root task user the permissions to access the SANDBOX_PATH volume of PARENT type

[ https://issues.apache.org/jira/browse/MESOS-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550481#comment-16550481 ] Qian Zhang commented on MESOS-8810: --- RR: https://reviews.apache.org/r/67996/ > Grant non-root task

[jira] [Comment Edited] (MESOS-7176) Add versioning support to network/cni isolator

[ https://issues.apache.org/jira/browse/MESOS-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374228#comment-16374228 ] Qian Zhang edited comment on MESOS-7176 at 7/20/18 1:19 AM: According to [CNI

[jira] [Created] (MESOS-9076) Mesos agent will be wrongly treated as unknown orphaned container if `--cgroups_root` has a leading slash

Qian Zhang created MESOS-9076: - Summary: Mesos agent will be wrongly treated as unknown orphaned container if `--cgroups_root` has a leading slash Key: MESOS-9076 URL: https://issues.apache.org/jira/browse/MESOS-9076

[jira] [Commented] (MESOS-9076) Mesos agent will be wrongly treated as unknown orphaned container if `--cgroups_root` has a leading slash

[ https://issues.apache.org/jira/browse/MESOS-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544871#comment-16544871 ] Qian Zhang commented on MESOS-9076: --- The root cause of this issue is, a leading slash in

<    1   2   3   4   5   6   7   8   9   >