[jira] [Commented] (MESOS-10156) Enable the `volume/csi` isolator in UCR
[ https://issues.apache.org/jira/browse/MESOS-10156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190876#comment-17190876 ] Greg Mann commented on MESOS-10156: --- {noformat} commit a8059a78473774e3d95e8e908f360ee5e9aadd0d Author: Greg Mann Date: Fri Sep 4 10:39:10 2020 -0700 Added tests for 'volume/csi' isolator recovery. Review: https://reviews.apache.org/r/72806/ {noformat} > Enable the `volume/csi` isolator in UCR > --- > > Key: MESOS-10156 > URL: https://issues.apache.org/jira/browse/MESOS-10156 > Project: Mesos > Issue Type: Task >Reporter: Qian Zhang >Assignee: Qian Zhang >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MESOS-10157) Add documentation for the `volume/csi` isolator
[ https://issues.apache.org/jira/browse/MESOS-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-10157: - Assignee: Greg Mann > Add documentation for the `volume/csi` isolator > --- > > Key: MESOS-10157 > URL: https://issues.apache.org/jira/browse/MESOS-10157 > Project: Mesos > Issue Type: Task >Reporter: Qian Zhang >Assignee: Greg Mann >Priority: Major > Labels: docs, documentation > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MESOS-10184) Executor registration timing out may result in incorrect task status update message incorrect message can be sent in the status update.
Andrei Sekretenko created MESOS-10184: - Summary: Executor registration timing out may result in incorrect task status update message incorrect message can be sent in the status update. Key: MESOS-10184 URL: https://issues.apache.org/jira/browse/MESOS-10184 Project: Mesos Issue Type: Bug Affects Versions: 1.8.1 Reporter: Andrei Sekretenko Example (the identifiers are fake) {noformat} I0903 16:50:27.584743 19083 slave.cpp:7149] Terminating executor 'foobar' of framework 81fc320c7-74ab-4f69-9e85-ead606264c3- because it did not register within 10mins I0903 16:50:27.584909 19083 containerizer.cpp:2580] Destroying container 8804fa0c-fafb-408c-8c68-5e0767267942 in PROVISIONING state I0903 16:50:27.584928 19083 containerizer.cpp:3277] Transitioning the state of container 8804fa0c-fafb-408c-8c68-5e0767267942 from PROVISIONING to DESTROYING E0903 16:50:27.585126 19053 slave.cpp:6526] Container '8804fa0c-fafb-408c-8c68-5e0767267942' for executor 'foobar' of framework 81fc320c7-74ab-4f69-9e85- {noformat} The master and the scheduler are getting TASK_FAILED update with a message "(Failed to launch container: discarded)" which is totally misleading. -- This message was sent by Atlassian Jira (v8.3.4#803005)