[
https://issues.apache.org/jira/browse/MESOS-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712076#comment-14712076
]
Alexander Rukletsov commented on MESOS-2865:
--------------------------------------------
Libprocess relies on TCP for message delivery. I don't think libprocess waits
for acks before sending more messages, I think [~arojas] can provide more info
on that. In absence of failovers, I can see no reasons why individual messages
can be randomly dropped and not delivered by network stack. If a disconnect
occurs, then, of course, messages won't be delivered, but this is a different
story. However, delivery doesn't guarantee processing; the only way to
guarantee processing is to send an ack, which is done for all status update
messages and only for them.
> 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)
