Thank you Adam
When you say:but before you upgrade Mesos to 0.23, you should upgrade
your scheduler (and executor) libmesos to 0.22.x
Do you mean - recompile?
Does this sentence from link with upgrade instructions you provided means the
same? Rebuild and install any modules so that upgraded
Yes, you'll have to recompile your scheduler/executor against the latest
libmesos.
In the upgrade guide, this is mentioned as Upgrade the schedulers by
linking the latest native library / jar / egg (if necessary).
The modules instructions apply to C++ plugins for the Mesos master/slaves
Hello guys,
I wonder about compatibility of Mesos protobuf for Myriad usage.
If I complied Myriad with Mesos version 0.22.1/0.21.1 but on the cluster I have
Mesos 0.23 - is it suppose to be compatible?
Yesterday our guys came across an exception(see below).
When switching jars to mesos-0.21.1
[
https://issues.apache.org/jira/browse/MYRIAD-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Marella updated MYRIAD-7:
-
Issue Type: Improvement (was: Bug)
Run MyriadMesosScheduler inside YARN's resource manager JVM.
[
https://issues.apache.org/jira/browse/MYRIAD-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Marella reopened MYRIAD-7:
--
Assignee: Santosh Marella
Run MyriadMesosScheduler inside YARN's resource manager JVM.
[
https://issues.apache.org/jira/browse/MYRIAD-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santosh Marella updated MYRIAD-55:
--
Issue Type: Improvement (was: Bug)
Add a API to destroy a Myriad/YARN cluster