[jira] [Assigned] (MESOS-10038) Implement agent code to listen on a domain socket
[ https://issues.apache.org/jira/browse/MESOS-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benno Evers reassigned MESOS-10038: --- Assignee: Benjamin Bannier > Implement agent code to listen on a domain socket > - > > Key: MESOS-10038 > URL: https://issues.apache.org/jira/browse/MESOS-10038 > Project: Mesos > Issue Type: Task >Reporter: Benno Evers >Assignee: Benjamin Bannier >Priority: Major > > On an agent with executor domain sockets enabled, we need to implement code > such that the agent listens for incoming connections on its domain sockets, > and creates `Connection` objects through which executor <-> agent v1 > communication can happen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10055) Update Mesos UI to display the resource limits of tasks
Qian Zhang created MESOS-10055: -- Summary: Update Mesos UI to display the resource limits of tasks Key: MESOS-10055 URL: https://issues.apache.org/jira/browse/MESOS-10055 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10052) Update cgroup isolator to support nested cgroups for nested containers
Qian Zhang created MESOS-10052: -- Summary: Update cgroup isolator to support nested cgroups for nested containers Key: MESOS-10052 URL: https://issues.apache.org/jira/browse/MESOS-10052 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10054) Update Docker containerizer set Docker container’s resource limits and `oom_score_adj`
Qian Zhang created MESOS-10054: -- Summary: Update Docker containerizer set Docker container’s resource limits and `oom_score_adj` Key: MESOS-10054 URL: https://issues.apache.org/jira/browse/MESOS-10054 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10053) Update Docker executor to set Docker container’s resource limits and `oom_score_adj`
Qian Zhang created MESOS-10053: -- Summary: Update Docker executor to set Docker container’s resource limits and `oom_score_adj` Key: MESOS-10053 URL: https://issues.apache.org/jira/browse/MESOS-10053 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10050) Update the `update()` method of containerizer to handle container resource limits
Qian Zhang created MESOS-10050: -- Summary: Update the `update()` method of containerizer to handle container resource limits Key: MESOS-10050 URL: https://issues.apache.org/jira/browse/MESOS-10050 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10051) Update the `LaunchContainer` agent API to support container resource limits
Qian Zhang created MESOS-10051: -- Summary: Update the `LaunchContainer` agent API to support container resource limits Key: MESOS-10051 URL: https://issues.apache.org/jira/browse/MESOS-10051 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10049) Add a new reason in `TaskStatus::Reason` for the case that a task is OOM-killed due to exceeding its memory request
Qian Zhang created MESOS-10049: -- Summary: Add a new reason in `TaskStatus::Reason` for the case that a task is OOM-killed due to exceeding its memory request Key: MESOS-10049 URL: https://issues.apache.org/jira/browse/MESOS-10049 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10048) Update the memory subsystem in the cgroup isolator to set container’s memory resource limits and `oom_score_adj`
Qian Zhang created MESOS-10048: -- Summary: Update the memory subsystem in the cgroup isolator to set container’s memory resource limits and `oom_score_adj` Key: MESOS-10048 URL: https://issues.apache.org/jira/browse/MESOS-10048 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10047) Update the CPU subsystem in the cgroup isolator to set container’s CPU resource limits
Qian Zhang created MESOS-10047: -- Summary: Update the CPU subsystem in the cgroup isolator to set container’s CPU resource limits Key: MESOS-10047 URL: https://issues.apache.org/jira/browse/MESOS-10047 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10046) Launch executor container with resource limits
Qian Zhang created MESOS-10046: -- Summary: Launch executor container with resource limits Key: MESOS-10046 URL: https://issues.apache.org/jira/browse/MESOS-10046 Project: Mesos Issue Type: Task Reporter: Qian Zhang We need to add resource limits into `ContainerConfig` first, and then set the resources limits in it according to the executor/task resource limits when launching executor container. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10045) Validate task’s resources limits in Mesos master
Qian Zhang created MESOS-10045: -- Summary: Validate task’s resources limits in Mesos master Key: MESOS-10045 URL: https://issues.apache.org/jira/browse/MESOS-10045 Project: Mesos Issue Type: Task Reporter: Qian Zhang When launching a task, we need to validate: # Only CPU and memory are supported as resource limits. # Resource limit must be larger than resource request. # `TaskInfo` can only include resource limits when the relevant agent possesses the TASK_RESOURCE_LIMITS capability. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10044) Add a new capability `TASK_RESOURCE_LIMITS` into Mesos agent
Qian Zhang created MESOS-10044: -- Summary: Add a new capability `TASK_RESOURCE_LIMITS` into Mesos agent Key: MESOS-10044 URL: https://issues.apache.org/jira/browse/MESOS-10044 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10043) Add resource limits into the protobuf message `TaskInfo` and `Task`
Qian Zhang created MESOS-10043: -- Summary: Add resource limits into the protobuf message `TaskInfo` and `Task` Key: MESOS-10043 URL: https://issues.apache.org/jira/browse/MESOS-10043 Project: Mesos Issue Type: Task Reporter: Qian Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10037) Create code to bind-mount domain sockets into executor containers
[ https://issues.apache.org/jira/browse/MESOS-10037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benno Evers reassigned MESOS-10037: --- Assignee: Benno Evers > Create code to bind-mount domain sockets into executor containers > - > > Key: MESOS-10037 > URL: https://issues.apache.org/jira/browse/MESOS-10037 > Project: Mesos > Issue Type: Task >Reporter: Benno Evers >Assignee: Benno Evers >Priority: Major > > On an agent with domain socket communication enabled, when a new executor is > launched, the agent should bind-mount the domain socket into the executor's > root directory. > On a failure to create the mount, the task launch should fail with the new > reason `REASON_BIND_MOUNT_FAILED`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10036) Implement agent code to create a domain socket on startup
[ https://issues.apache.org/jira/browse/MESOS-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benno Evers reassigned MESOS-10036: --- Assignee: Benno Evers > Implement agent code to create a domain socket on startup > - > > Key: MESOS-10036 > URL: https://issues.apache.org/jira/browse/MESOS-10036 > Project: Mesos > Issue Type: Task >Reporter: Benno Evers >Assignee: Benno Evers >Priority: Major > > When implementing the design proposed in > https://docs.google.com/document/d/1RUvjoBvM3UX_lLcq_J_crWpMMn3nO8CY0KWc655ELsM/edit > , in the case where we enable domain socket communication we need some code > in the agent that checks on startup whether a domain socket already exists at > the location pointed to by flags.domain_socket_location, and if not creates a > new listening socket bound to that path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-10036) Implement agent code to create a domain socket on startup
[ https://issues.apache.org/jira/browse/MESOS-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983447#comment-16983447 ] Benno Evers commented on MESOS-10036: - https://reviews.apache.org/r/71832/ https://reviews.apache.org/r/71833/ > Implement agent code to create a domain socket on startup > - > > Key: MESOS-10036 > URL: https://issues.apache.org/jira/browse/MESOS-10036 > Project: Mesos > Issue Type: Task >Reporter: Benno Evers >Priority: Major > > When implementing the design proposed in > https://docs.google.com/document/d/1RUvjoBvM3UX_lLcq_J_crWpMMn3nO8CY0KWc655ELsM/edit > , in the case where we enable domain socket communication we need some code > in the agent that checks on startup whether a domain socket already exists at > the location pointed to by MESOS_DOMAIN_SOCKET, and if not creates a new > listening socket bound to that path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10042) Mesos UI template not always rendered
Damien Gerard created MESOS-10042: - Summary: Mesos UI template not always rendered Key: MESOS-10042 URL: https://issues.apache.org/jira/browse/MESOS-10042 Project: Mesos Issue Type: Bug Components: webui Affects Versions: 1.9.0 Environment: Linux Vivaldi & Firefox ubuntu 18.04 Reporter: Damien Gerard Attachments: image-2019-11-27-17-34-29-733.png, image-2019-11-27-17-37-18-679.png, image-2019-11-27-17-39-06-984.png, image-2019-11-27-17-39-16-491.png, image-2019-11-27-17-39-37-341.png, image-2019-11-27-17-39-44-306.png When opening the webui directly or when switching tabs (by clicking on "Frameworks"/"Agents"/whatever back to the main page), the page is not always rendered (see as below). !image-2019-11-27-17-39-37-341.png! Also, the cluster name is never replaced (the same in our mesos 1.6) even if --cluster "some-value" is set !image-2019-11-27-17-39-44-306.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
