Thanks. I'm going to try a solution where I count slaves by querying the endpoint on the mesos master, then use that number to update the instance count of the app in marathon using the rest endpoint.
With the constraints mentioned earlier, I should get close to running on all slaves with no manual intervention required. I'll post findings here. -------- Original message -------- From: "Heller, Chris" <[email protected]> Date:11/11/2014 9:01 AM (GMT-05:00) To: [email protected] Cc: Subject: Re: Running a Marathon Task on every active slave If you are OK with a fixed number of slaves. You could set the number of instances equal to the number of slaves, and then set the constraints of the job to: "constraints": [[ "hostname", "UNIQUE" ]]. -Chris From: Leigh Martell <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, November 11, 2014 at 8:56 AM To: "[email protected]" <[email protected]> Subject: Re: Running a Marathon Task on every active slave Hey David, Yes"ish" from my understanding with the host name constraint(to restrict 1 per host) you can do this but you will need prior knowledge of the amount of slaves. Here is my reference https://mesosphere.github.io/marathon/docs/constraints.html Hope that helps! -Leigh On Tue, Nov 11, 2014 at 9:31 AM, David J. Palaitis <[email protected]> wrote: I'd like to have Marathon keep a single, running instance of my command on every active slave in the cluster. Is it possible?
