Marathon runs atop Apache Mesos. You can install Mesos via your system’s package manager. Current builds and instructions on how to set up repositories for major Linux distributions are available on the Mesosphere downloads page.
If you want to build Mesos from source, see the
Mesos Getting Started page or the
Mesosphere tutorial
for details. Running make install
will install Mesos in /usr/local
.
Please see the documentation on Marathon native package repositories.
Download and unpack the latest Marathon release.
$ curl -O http://downloads.mesosphere.com/marathon/v1.5.1/marathon-1.5.1.tgz
$ tar xzf marathon-1.5.1.tgz
SHA-256 checksums are available by appending .sha256
to the URLs.
See the Marathon upgrade guide to learn how to upgrade to a new version.
Both ZooKeeper and Mesos need to be running in order to launch Marathon in high availability mode.
Point your web browser to
localhost:8080
and you should see the Marathon UI.
$ ./bin/marathon --master zk://zk1.foo.bar:2181,zk2.foo.bar:2181/mesos --zk zk://zk1.foo.bar:2181,zk2.foo.bar:2181/marathon
Marathon uses --master
to find the Mesos masters, and --zk
to find ZooKeepers
for storing state. They are separate options because Mesos masters can also be
discovered in other ways.
For all configuration options, see the command line flags doc. For more information on the high-availability feature of Marathon, see the high availability doc.
MESOS_NATIVE_JAVA_LIBRARY
: bin/marathon
searches the common installation paths,
/usr/lib
and /usr/local/lib
, for the Mesos native library. If the
library lives elsewhere in your configuration, set the environment variable
MESOS_NATIVE_JAVA_LIBRARY
to its full path.
For example:
$ MESOS_NATIVE_JAVA_LIBRARY=/Users/bob/libmesos.dylib ./bin/start --master local --zk zk://localhost:2181/marathon
For an introduction to Marathon application definitions and how they are executed, see Application Basics.