stale framework registrations

I recently stopped Marathon but it is still registered with the Mesos Masters. I started a new instance of Marathon and it has re-registered successfully with a new framework Id. I'd like to understand how to force deregistration of the stale framework.

RE: stale framework registrations

, 2014 at 9:48 AM, David Palaitis david.palai...@twosigma.commailto:david.palai...@twosigma.com wrote: I recently stopped Marathon but it is still registered with the Mesos Masters. I started a new instance of Marathon and it has re-registered successfully with a new framework Id. I’d like

RE: stale framework registrations

[mailto:vi...@twitter.com] On Behalf Of Vinod Kone Sent: Tuesday, August 05, 2014 8:11 PM To: user@mesos.apache.org Subject: Re: stale framework registrations On Tue, Aug 5, 2014 at 4:58 PM, David Palaitis david.palai...@twosigma.commailto:david.palai...@twosigma.com wrote: It’s still registered

RE: Spark scheduler receives no offers after some time

I’m running up against this issue w/ Mesos 0.19 and Spark 1.0.1 - https://www.mail-archive.com/issues@spark.apache.org/msg06732.html Caused by: javax.security.auth.login.LoginException: unable to find LoginModule class: org/apache/hadoop/security/UserGroupInformation$HadoopLoginModule

Cassandra Mesos Framework Issue

I am having trouble getting Cassandra Mesos to work in a simple test environment. The framework connects, but tasks get lost with the following error. 215872 [Thread-113] INFO mesosphere.cassandra.CassandraScheduler - Got new resource offers ArrayBuffer(abc.def.ghi.com) 215875 [Thread-113]

RE: Cassandra Mesos Framework Issue

tutorial are you working from? On 18 October 2014 15:08, David Palaitis david.palai...@twosigma.com wrote: I am having trouble getting Cassandra Mesos to work in a simple test environment. The framework connects, but tasks get lost with the following error. 215872 [Thread-113] INFO

Re: Scheduler for distributed builds

Cookies a fit in the case where you have more jobs than resources available to run them. It manages large job queues, prioritizes jobs and balances resources fairly across users, or roles, etc. Cook is dfntly interesting for a build farm e.g distributed Basel, although the scheduling overhead

Re: MesosCon 2018 Location Change

I’d be happy to support a mini-con / meetup in NYC at the same time. Reach out if you’re interested. > On Aug 26, 2018, at 1:02 AM, Vaibhav Khanduja > wrote: > > +1 for bay area. > > Thx > >> On Sat, Aug 25, 2018, 3:20 PM Jörg Schad wrote: >> Just one more comment on the reasoning here: