After a recent power outage, it became clear that the defaults that the Mesosphere-provided packages set regarding to init need tweaking, depending on your config.
In our case, we have numerous blade servers within chassis, and each chassis gets 1 mesos master. All of the blades within all of the chassis are slaves (including the masters), but only the masters themselves need to have zookeeper and mesos-master started automatically.
By default, the Ubuntu packages for Mesosphere enable mesos-master, zookeeper, and chronos to all start automatically, which isn't really ideal.
It should be noted that I haven't opened a bug on this with the Mesosphere folks yet, though I think that the services shouldn't be enabled until the configs are actually valid.
No comments:
Post a Comment