You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2016/02/09 02:36:18 UTC

[jira] [Updated] (MESOS-4571) SlaveRecoveryTest.RecoverStatusUpdateManager is not consistent with its description

     [ https://issues.apache.org/jira/browse/MESOS-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-4571:
------------------------------
    Shepherd: Vinod Kone

yes.

> SlaveRecoveryTest.RecoverStatusUpdateManager is not consistent with its description
> -----------------------------------------------------------------------------------
>
>                 Key: MESOS-4571
>                 URL: https://issues.apache.org/jira/browse/MESOS-4571
>             Project: Mesos
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Shuai Lin
>            Assignee: Shuai Lin
>              Labels: newbie++
>
> The description is:
> {code}
> The slave is killed before the update reaches the scheduler. When the slave comes back up it resends the unacknowledged update"
> {code}
> But in the test code, the {{StatusUpdateMessage}} is dropped, so there is no checkpointing for status update involved at all. It's the executor resends the unacknowledged status updates when reconnecting, rather than the slave "resends the unacknowledged update". This means this test is the same with {{SlaveRecoveryTest.ReconnectExecutor}}, which doesn't make sense.
> To fix it, we should drop the {{StatusUpdateAcknowledgementMessage}} instead of the {{StatusUpdateMessage}}.



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