Hi Igor, You made a good point about the tradeoffs. I think the main thing you would get with Marathon is the accounting for resources (the memory and cpus specified in the config file). That allows Mesos to manage the resources properly. I don't think the other tools mentioned would reserve resources from Mesos.
If you want more information about production ops for Mesos, you might want to ask in the Mesos mailing list. Or, you can check out the https://dcos.io/community/ project. Susan On Sat, Jan 20, 2018 at 11:59 PM, igor.berman <igor.ber...@gmail.com> wrote: > Hi Susan > > In general I can get what I need without Marathon, with configuring > external-shuffle-service with puppet/ansible/chef + maybe some alerts for > checks. > > I mean in companies that don't have strong Devops teams and want to install > services as simple as possible just by config - Marathon might be useful, > however if company already has strong puppet/ansible/chef whatever infra, > the Marathon addition(additional component) and management is less clear > > WDYT? > > > > -- > Sent from: http://apache-spark-user-list.1001560.n3.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe e-mail: user-unsubscr...@spark.apache.org > > -- Susan X. Huynh Software engineer, Data Agility xhu...@mesosphere.com
