[
https://issues.apache.org/jira/browse/MESOS-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105874#comment-16105874
]
Yan Xu commented on MESOS-7714:
-------------------------------
I see, but 1) is a real operational concern for upgrading to 1.4 right? I
wouldn't want to upgrade my agents to 1.4 knowing I won't be able to roll them
back once refined reservations are made (i.e., after they are used for a
while)...
I think to support 1) we have to support 'pre-reservation-refinement' for a
while (across 1.x versions?)
https://github.com/apache/mesos/blob/master/docs/versioning.md#upgrades
mentions upgrades but not downgrades but I don't see how it would work if
downgrades are not implicitly covered by the same guarantee...
Thoughts?
> Fix agent downgrade for reservation refinement
> ----------------------------------------------
>
> Key: MESOS-7714
> URL: https://issues.apache.org/jira/browse/MESOS-7714
> Project: Mesos
> Issue Type: Bug
> Reporter: Michael Park
> Priority: Blocker
>
> The agent code only partially supports downgrading of an agent correctly.
> The checkpointed resources are done correctly, but the resources within
> the {{SlaveInfo}} message as well as tasks and executors also need to be
> downgraded
> correctly and converted back on recovery.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)