You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2014/10/31 08:07:34 UTC
[jira] [Resolved] (MESOS-1414) Status updates should not be sent
from the slave until it is registered.
[ https://issues.apache.org/jira/browse/MESOS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B resolved MESOS-1414.
---------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Assignee: Vinod Kone (was: Craig Hansen-Sturm)
Target Version/s: 0.21.0
commit 65c3c3639b385d880dbfe10bc4f652655695c8b3
Author: Vinod Kone <vi...@gmail.com>
Date: Fri Oct 17 15:26:52 2014 -0700
Added pause() and resume() to status update manager.
Review: https://reviews.apache.org/r/26957
commit e64dda411bc83963179c92ae71caefa8d21b54b4
Author: Vinod Kone <vi...@gmail.com>
Date: Wed Oct 15 18:22:46 2014 -0700
Updated status update manager to forward updates via slave.
Review: https://reviews.apache.org/r/26846
> Status updates should not be sent from the slave until it is registered.
> ------------------------------------------------------------------------
>
> Key: MESOS-1414
> URL: https://issues.apache.org/jira/browse/MESOS-1414
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.19.0
> Reporter: Benjamin Mahler
> Assignee: Vinod Kone
> Fix For: 0.21.0
>
>
> Currently, status updates are sent from the slave once a master is detected, instead of waiting for the slave to be registered.
> The master currently drops updates that arrive while the slave is not activated, so this is harmless but causes an unnecessary amount of dropped messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)