4 ms·

I'll outline the specific goals of both Marathon / Chronos to clear any confusion: Marathon: Execute a long running job in the cluster and make sure it keeps o

I'll outline the specific goals of both Marathon / Chronos to clear any confusion: Marathon: Execute a long running job in the cluster and make sure it keeps on running. You can specify resource requirements as well as how many instances of this job you want to run. Examples of jobs: Rails App, Jetty Service, JBoss Service. Chronos: You can specify a repeating & finite job based on a schedule or another job completing. You specify resource requirements. Examples of jobs: Mysqldump (e.g. daily dump prod DB), Hadoop Job (cascading, pig, cascalog, scalding...), bash script using ImageMagick to create thumbnails. Both of these systems are Mesos frameworks - Mesos does the heavy lifting and offers resources to these frameworks which the frameworks can accept or reject. You can find more info here: http://mesos.apache.org/ http://mesos.apache.org/

peterwwillis 13y ago
Thank you for the reply, I appreciate it. But from everything i've read (all the documentation for these frameworks suck, though Mason's is the most readable) still seems like Mesos supports the features of the previous two tools, for the most part. Is there some reason its feature set wasn't just tweaked a bit to handle those two cases? Like, why is there a distinction between a long-running and a short-running job? Repeating a job is also not an especially complicated task that should require a whole new framework to accomplish. The reason i'm asking these questions is I want to know if I need to use these tools. It seems like kids these days just immediately grab up every new tool they can and try to shove them into their environment, vs trying to find the right fit or configure them properly. It feels like Marathon and Chronos are mostly unnecessary - this is evident once you realize Mesos is a framework you can build on to do the same things Marathon and Chronos do with a lot less complexity.
- florianleibert 13y ago
  If you have specific requests on how to make the docs for these frameworks better, it'd be great if you filed a ticket on their respective github page.

peterwwillis 13y ago

Thank you for the reply, I appreciate it. But from everything i've read (all the documentation for these frameworks suck, though Mason's is the most readable) still seems like Mesos supports the features of the previous two tools, for the most part. Is there some reason its feature set wasn't just tweaked a bit to handle those two cases? Like, why is there a distinction between a long-running and a short-running job? Repeating a job is also not an especially complicated task that should require a whole new framework to accomplish. The reason i'm asking these questions is I want to know if I need to use these tools. It seems like kids these days just immediately grab up every new tool they can and try to shove them into their environment, vs trying to find the right fit or configure them properly. It feels like Marathon and Chronos are mostly unnecessary - this is evident once you realize Mesos is a framework you can build on to do the same things Marathon and Chronos do with a lot less complexity.

florianleibert 13y ago
If you have specific requests on how to make the docs for these frameworks better, it'd be great if you filed a ticket on their respective github page.