mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bmahler <...@git.apache.org>
Subject [GitHub] mesos pull request #181: Add elastic-job -cloud description into frameworks....
Date Tue, 22 Nov 2016 02:17:23 GMT
Github user bmahler commented on a diff in the pull request:

    https://github.com/apache/mesos/pull/181#discussion_r89031974
  
    --- Diff: docs/frameworks.md ---
    @@ -30,6 +30,7 @@ layout: documentation
     
     * [Chronos](https://github.com/mesos/chronos) is a distributed job scheduler that supports
complex job topologies. It can be used as a more fault-tolerant replacement for Cron.
     * [Cook](https://github.com/twosigma/cook) is a job scheduler like Torque that not only
supports individual tasks, but also Spark. Cook provides powerful automatic preemption and
multitenancy features for shared clusters, in order to guarantee throughput to all users while
allowing individuals to temporarily "burst" to additional resources as needed. Cook provides
a simple REST API & Java client for interaction.
    +* [Elastic-Job-Cloud](https://github.com/dangdangdotcom/elastic-job) is a distributed
scheduled job cloud solution. It focus on scale out, fault-tolerant(failover, misfire), flexible
job scenarios(transient, daemon), complex trigger(cron, event driven), extra job templates(dataflow),
jobs running history trace.
    --- End diff --
    
    How about "is a distributed scheduled job cloud solution designed with HA and fault-tolerance
in mind. It focuses on horizontal scaling, and provides transient and daemon jobs, event and
schedule based job triggers, job dependencies, and job history."
    
    I tried to rephrase this a bit, does it still sound accurate?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message