commit | 284f40f5e36c70114e6229fcb93e3b203d2f1120 | [log] [tgz] |
---|---|---|
author | Bill Farner <wfarner@apache.org> | Tue Nov 28 16:58:47 2017 -0800 |
committer | Bill Farner <wfarner@apache.org> | Tue Nov 28 16:58:47 2017 -0800 |
tree | ac328b012812ebcb868a4097703dd3fc9842f070 | |
parent | 80139da4624916e406c7e80c4ea2d286d4d859c3 [diff] |
Add RemoveJobUpdates log Op, slim JobUpdateStore API JobUpdateStore historically had granular APIs in the storage layer to minimize unnecessary use of 'expensive' database objects. The in-memory store makes these 'free', so moving business logic out of the storage layer is now feasible for performance and pragmatic. This patch also introduces the `RemoveJobUpdates` log `Op`, and `PruneJobUpdateHistory` is now ignored. In a future release (and possibly before, with a feature flag), the scheduler will write `RemoveJobUpdates` to the log. LogStorage has always had the fundamental expectation that `Op`s are idempotent. The job update event `Op`s arguably violate this requirement, but at minimum, explicit removal of updates is necessary for idempotency. From LogStorage.java: This design implies that all mutations must be idempotent and free from constraint and thus replayable over newer operations when recovering from an old checkpoint. Reviewed at https://reviews.apache.org/r/63884/
Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It supports running long-running services, cron jobs, and ad-hoc jobs. Aurora aims to make it extremely quick and easy to take a built application and run it on machines in a cluster, with an emphasis on reliability. It provides basic operations to manage services running in a cluster, such as rolling upgrades.
To very concisely describe Aurora, it is like a distributed monit or distributed supervisord that you can instruct to do things like run 100 of these, somewhere, forever.
Aurora is built for users and operators.
User-facing Features:
Under the hood, to help you rest easy:
Aurora can take over for most uses of software like monit and chef. Aurora can manage applications, while these tools are still useful to manage Aurora and Mesos themselves.
However, if you have very specific scheduling requirements, or are building a system that looks like a scheduler itself, you may want to explore developing your own framework.
Are you using Aurora too? Let us know, or submit a patch to join the list!
If you have questions that aren‘t answered in our documentation, you can reach out to one of our mailing lists. We’re also often available in IRC: #aurora on irc.freenode.net.
You can also file bugs/issues in our JIRA queue.
Except as otherwise noted this software is licensed under the Apache License, Version 2.0
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.