[jira] [Created] (MESOS-10004) Enable SSL on Windows
Greg Mann created MESOS-10004: - Summary: Enable SSL on Windows Key: MESOS-10004 URL: https://issues.apache.org/jira/browse/MESOS-10004 Project: Mesos Issue Type: Epic Reporter: Greg Mann -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10003) Design doc for SSL on Windows
Greg Mann created MESOS-10003: - Summary: Design doc for SSL on Windows Key: MESOS-10003 URL: https://issues.apache.org/jira/browse/MESOS-10003 Project: Mesos Issue Type: Task Components: libprocess Reporter: Greg Mann -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10002) Design doc for container bursting
Greg Mann created MESOS-10002: - Summary: Design doc for container bursting Key: MESOS-10002 URL: https://issues.apache.org/jira/browse/MESOS-10002 Project: Mesos Issue Type: Task Components: agent, containerization Reporter: Greg Mann -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10001) Container bursting for CPU/mem
Greg Mann created MESOS-10001: - Summary: Container bursting for CPU/mem Key: MESOS-10001 URL: https://issues.apache.org/jira/browse/MESOS-10001 Project: Mesos Issue Type: Epic Components: agent, containerization Reporter: Greg Mann -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-6480) Support for docker live-restore option in Mesos
[ https://issues.apache.org/jira/browse/MESOS-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942893#comment-16942893 ] Andrei Budnik commented on MESOS-6480: -- design doc: [https://docs.google.com/document/d/1JeLTr9L31S8eIg-6xpjedIUKvnfNake0kPTzxEwdUdI] > Support for docker live-restore option in Mesos > --- > > Key: MESOS-6480 > URL: https://issues.apache.org/jira/browse/MESOS-6480 > Project: Mesos > Issue Type: Task >Reporter: Milind Chawre >Priority: Major > > Docker-1.12 supports live-restore option which keeps containers alive during > docker daemon downtime https://docs.docker.com/engine/admin/live-restore/ > I tried to use this option in my Mesos setup And observed this : > 1. On mesos worker node stop docker daemon. > 2. After some time start the docker daemon. All the containers running on > that are still visible using "docker ps". This is an expected behaviour of > live-restore option. > 3. When I check mesos and marathon UI. It shows no Active tasks running on > that node. The containers which are still running on that node are now > scheduled on different mesos nodes, which is not right since I can see the > containers in "docker ps" output because of live-restore option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-3938) Consider allowing setting quotas for the default '*' role.
[
https://issues.apache.org/jira/browse/MESOS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942888#comment-16942888
]
Meng Zhu commented on MESOS-3938:
-
{noformat}
commit 270a3dce490d5b334f9a0011ea416ffc42e187e4
Author: Meng Zhu
Date: Wed Sep 25 15:41:07 2019 -0700
Documented setting quota on the default role in the release note.
Review: https://reviews.apache.org/r/71548
commit 4dd00c6ad3d8af1d38d496a51f5407ee0e4b1970
Author: Meng Zhu
Date: Tue Sep 10 11:51:09 2019 -0700
Allowed setting quota the default "*" role.
There is no clear argument against setting quota on the default
"*" role. This patch allows doing so. Tests are updated to check
against regressions.
Review: https://reviews.apache.org/r/71464
{noformat}
> Consider allowing setting quotas for the default '*' role.
> --
>
> Key: MESOS-3938
> URL: https://issues.apache.org/jira/browse/MESOS-3938
> Project: Mesos
> Issue Type: Task
>Reporter: Alex R
>Assignee: Meng Zhu
>Priority: Major
> Labels: resource-management
>
> Investigate use cases and implications of the possibility to set quota for
> the '*' role. For example, having quota for '*' set can effectively reduce
> the scope of the quota capacity heuristic.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MESOS-9962) Mesos may report completed task as running in the state.
[ https://issues.apache.org/jira/browse/MESOS-9962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier reassigned MESOS-9962: --- Assignee: Benjamin Bannier > Mesos may report completed task as running in the state. > > > Key: MESOS-9962 > URL: https://issues.apache.org/jira/browse/MESOS-9962 > Project: Mesos > Issue Type: Bug > Components: agent >Reporter: Meng Zhu >Assignee: Benjamin Bannier >Priority: Major > Labels: foundations > > When the following steps occur: > 1) A graceful shutdown is initiated on the agent (i.e. SIGUSR1 or > /master/machine/down). > 2) The executor is sent a kill, and the agent counts down on > executor_shutdown_grace_period. > 3) The executor exits, before all terminal status updates reach the agent. > This is more likely if executor_shutdown_grace_period passes. > This results in a completed executor, with non-terminal tasks (according to > status updates). > This would produce a confusing report where completed tasks are still > TASK_RUNNING. -- This message was sent by Atlassian Jira (v8.3.4#803005)
