binMake chronos the PID 1 (#795)Balthazar Rouberol3 months ago
docsReplace 'slave' with 'agent' in docs.Brenden Matthews2 months ago
integration-testsAdd integration tests. (#754)Brenden Matthews4 months ago
srcFix for nanosUntilNextJob() edge case. (#808)Brenden Matthews2 months ago
.gitignoreNew ui (#736)Brenden Matthews5 months ago
.mailmap.mailmap: put a.r.k..@gmail.com under a single namePierre Carrier4 years ago
.travis.ymlBuild fix, cache modules.Brenden Matthews4 months ago
DockerfileSet http_proxy for Docker build. (#751)Brenden Matthews4 months ago
LICENSEUpdate 2015 Licensingelingg2 years ago
NOTICEUpdated Licenseelingg2 years ago
README.mdUpdate README.mdBrenden Matthews2 months ago
build-release.shSet http_proxy for Docker build. (#751)Brenden Matthews4 months ago
build.xmlBuild fixes.Brenden Matthews4 months ago
changelog.mdMade `changelog.md` point to the releases page. (#755)Gastón Kleiman4 months ago
pom.xmlBump version in pom.xml.Brenden Matthews1 month ago

Chronos Build Status

Chronos is a replacement for cron. It is a distributed and fault-tolerant scheduler that runs on top of Apache Mesos that can be used for job orchestration. It supports custom Mesos executors as well as the default command executor. Thus by default, Chronos executes sh (on most systems bash) scripts.

Chronos can be used to interact with systems such as Hadoop (incl. EMR), even if the Mesos agents on which execution happens do not have Hadoop installed. Included wrapper scripts allow transfering files and executing them on a remote machine in the background and using asynchronous callbacks to notify Chronos of job completion or failures. Chronos is also natively able to schedule jobs that run inside Docker containers.

Chronos has a number of advantages over regular cron. It allows you to schedule your jobs using ISO8601 repeating interval notation, which enables more flexibility in job scheduling. Chronos also supports the definition of jobs triggered by the completion of other jobs. It supports arbitrarily long dependency chains.

The easiest way to use Chronos is to use DC/OS and install chronos via the universe.

Features

  • Web UI
  • ISO8601 Repeating Interval Notation
  • Handles dependencies
  • Job Stats (e.g. 50th, 75th, 95th and 99th percentile timing, failure/success)
  • Job History (e.g. job duration, start time, end time, failure/success)
  • Fault Tolerance (leader/follower)
  • Configurable Retries
  • Multiple Workers (i.e. Mesos agents)
  • Native Docker support

Documentation and Support

Chronos documentation is available on the Chronos GitHub pages site.

Documentation for installing and configuring the full Mesosphere stack including Mesos and Chronos is available on the Mesosphere website.

For questions and discussions around Chronos, please use the Google Group "chronos-scheduler": Chronos Scheduler Group.

If you'd like to take part in design research and test new features in Chronos before they're released, please add your name to Mesosphere's UX Research list.

Packaging

Mesosphere publishes Docker images for Chronos to Dockerhub, at https://hub.docker.com/r/mesosphere/chronos/.

Contributing

Instructions on how to contribute to Chronos are available on the Contributing docs page.

License

The use and distribution terms for this software are covered by the Apache 2.0 License (http://www.apache.org/licenses/LICENSE-2.0.html) which can be found in the file LICENSE at the root of this distribution. By using this software in any fashion, you are agreeing to be bound by the terms of this license. You must not remove this notice, or any other, from this software.

Contributors

Reporting Bugs

Please see the support page for information on how to report bugs.

About FluentSend Feedback