Suppose I registered two frameworks namely marathon and chronos(both in role *)
one after another, successfully deployed and run one app app1 by marathon,
also deployed one cron app app2 by chronos, before app2 due or after app2
finished, I can't deploy and launch any new app by marathon
Folks,
if you build tooling around Mesos, please be advised that in current 0.22
Mesos release /stats.json endpoint is deprecated in favour of
/metrics/snapshot and will be removed in Mesos 0.23 release. If you rely on
/stats.json, please update your code to use the new endpoint instead.
Related
Correct, the issue we were seeing is that Chronos would decline the offer,
but Chronos would keep getting it back instead of it being offered to
Marathon. We were reproducing this issue on a cluster with a single
master/slave, which is a bit of an anti-pattern. I'm not sure if anyone was
able to
@Elizabeth, we did encountered the same issue.
I just verified that both mesos-0.20.1 and the latest mesos-0.22.0 work OK if I
comment chronos refuse filter, that makes the refuse second changed back to
default 5s, if not, both mesos versions fail.
2015年4月9日 上午8:48于 sujz.b...@qq.com写道：
@David, after receiving and declining offer for the first time, chronos's share
is still the smaller one, so mesos continues to provide offer to chronos
instead of marathon.
@Elizabeth, I will try with the latest mesos a moment later.
2015年4月9日 上午8:37于 Elizabeth Lingg
I believe that DRF is more of a right of first refusal. Even though
marathon's got the higher share, all that means is that chronos will get
the offer first; marathon will have to wait until chronos declines it.
On Wed, Apr 8, 2015 at 5:33 PM Elizabeth Lingg elizab...@mesosphere.io
wrote:
Hi,
6 matches
Mail list logo
