mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James DeFelice (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2865) intermittently the executor is not receiving TASK_KILLED
Date Wed, 26 Aug 2015 00:24:45 GMT

    [ https://issues.apache.org/jira/browse/MESOS-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712239#comment-14712239
] 

James DeFelice commented on MESOS-2865:
---------------------------------------

I'm wondering if it's sane for me to handle libprocess messages in a way that they may be
processed out of order, or if I have to preserve the ordering on a per-connection basis.

> intermittently the executor is not receiving TASK_KILLED
> --------------------------------------------------------
>
>                 Key: MESOS-2865
>                 URL: https://issues.apache.org/jira/browse/MESOS-2865
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.21.1, 0.23.0
>         Environment: {code}
> $ dpkg -l |grep -e mesos
> ii  mesos                               0.21.1-1.1.ubuntu1404            amd64      
 Cluster resource manager with efficient resource isolation
> $ uname -a
> Linux node-1 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
> {code}
>            Reporter: James DeFelice
>              Labels: mesosphere
>
> for details, log snippets see https://github.com/mesosphere/kubernetes-mesos/issues/328
> The slave logs that it's been asked to kill a pod, but the message is never logged as
received by the executor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message