Re: [jira] [Commented] (MESOS-8927) Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck.

I'm sorry for the duplicated messages. Accidentally pressed the wrong key shortcuts twice :( Unfortunately I don't have the log right now. IIRC the executor received the `KILL` event because the log I saw contained this line: https://github.com/apache/mesos/blob/7e11a2d39cc642944897d2480105db fd86

Re: [jira] [Commented] (MESOS-8927) Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck.

Unfortunately I don't have the log right now. IIRC the executor received the `KILL` event because the log I saw contained this line: https://github.com/apache/mesos/blob/7e11a2d39cc642944897d2480105dbfd860fa601/src/launcher/default_executor.cpp#L1236 But it didn't contain this line: On Wed, May 16

Re: [jira] [Commented] (MESOS-8927) Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck.

Unfortunately I don't have any log. IIRC the executor received the the `KILL` event because this is printed: On Wed, May 16, 2018 at 6:18 PM, Vinod Kone wrote: > Can you paste some logs here too if you have? > > On Wed, May 16, 2018 at 5:53 PM, Chun-Hung Hsiao (JIRA) > wrote: > > > > > [ ht

Re: [jira] [Commented] (MESOS-8927) Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck.

Can you paste some logs here too if you have? On Wed, May 16, 2018 at 5:53 PM, Chun-Hung Hsiao (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/MESOS-8927?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16478318#comment-16478318 ] > > Chu

Re: [mesos-mail] Re: [Performance WG] Notes from meeting today

+Judith There should be a recording. Judith, do you know where they get posted? Benjamin, glad to hear it's useful, I'll continue doing it! On Wed, May 16, 2018 at 4:41 PM Gilbert Song wrote: > Do we have the recorded video for this meeting? > > On Wed, May 16, 2018 at 1:54 PM, Benjamin Bannie

[Containerization WG] Sync Agenda for May 17th, 2018

Hi folks, Tomorrow's WG meeting starts at 9 am PST. The agenda: - [jpeach] Automatically populating device nodes allowed by the devices cgroup. - * Container Devices * - Command executor deprecat

Re: [mesos-mail] Re: [Performance WG] Notes from meeting today

Do we have the recorded video for this meeting? On Wed, May 16, 2018 at 1:54 PM, Benjamin Bannier < benjamin.bann...@mesosphere.io> wrote: > Hi Ben, > > thanks for taking the time to edit and share these detailed notes. Being > able to asynchronously see the great work folks are doing surfaced is

Re: [Performance WG] Notes from meeting today

Hi Ben, thanks for taking the time to edit and share these detailed notes. Being able to asynchronously see the great work folks are doing surfaced is great, especially when put into context with thought like here. Benjamin > On May 16, 2018, at 8:06 PM, Benjamin Mahler wrote: > > Hi folks, >

[Performance WG] Notes from meeting today

Hi folks, Here are some notes from the performance meeting today. (1) First I did a demo of flamescope, you can find it here: https://github.com/Netflix/flamescope It's a very useful tool, hopefully we can make it easier for users to generate the data that we can drop into flamescope when report

Container logger module interface change

Hi, I committed a patch that changed the container logger interface. The `prepare()` interface in the ContainerLogger now takes a ContainerCofig. This change is necessary for us to support per container control on logger behavior. Previously, it was only possi