[
https://issues.apache.org/jira/browse/MESOS-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-3448:
-----------------------------------
Component/s: fetcher
Thanks for the report! I'm tempted to close this out because we have generally
not been designing the components within the slave (now called agent) to be
compatible across versions. This adds quite a bit of difficulty vs. assuming
the slave components can be updated atomically.
Two suggestions:
(1) Ensure a restart occurs immediately after you upgrade libmesos + binaries
on the machine (not necessary for masters currently). This tends to be the
easiest approach.
(2) Allow more than one version to be installed on your machine, so that you
can have libmesos + binaries stored for each version independently. This lets
your upgrade consist of toggling which binary should be started next, while
allowing the already running agent to use the old helper binaries (e.g.
fetcher).
Hope this helps.
> Trying to Live Upgrade Mesos Slaves from 0.22.x to 0.23.x Causes New
> Executors to Fail
> --------------------------------------------------------------------------------------
>
> Key: MESOS-3448
> URL: https://issues.apache.org/jira/browse/MESOS-3448
> Project: Mesos
> Issue Type: Bug
> Components: fetcher
> Reporter: Paul Cavallaro
> Priority: Minor
>
> When live upgrading from Mesos 0.22.x to 0.23.x the old running mesos-0.22.x
> slaves call out to the newly instaleld 0.23.x fetcher and fails with:
> F0914 11:43:16.355821 28833 fetcher.cpp:415] CHECK_SOME(fetcherInfo): Missing
> required fields: sandbox_directory Failed to parse FetcherInfo: Missing
> required fields: sandbox_directory
> This is because the old 0.22.x slave does not include those fields
> apparently, that the 0.23.x fetcher requires.
> Here's another report of that happening:
> http://wilderness.apache.org/channels/?f=mesos/2015-07-29
> Just wanted to raise to attention that this makes it annoying to live upgrade
> from 0.22.x to 0.23.x which otherwise would be smooth.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
