commit | 81f231ccd10e960b1485482a859bc449914668ed | [log] [tgz] |
---|---|---|
author | Andrei Sekretenko <asekretenko@apache.org> | Thu Sep 17 21:44:53 2020 +0200 |
committer | Andrei Sekretenko <asekretenko@apache.org> | Tue Sep 22 12:23:46 2020 +0200 |
tree | 5c71dea257065dac5dbd1f541a7073ce14f2ce0c | |
parent | 7aee5a87d117601b0f551a68dac4ea25903e5f81 [diff] |
Tied the 1st hierarchical allocator process to a process ID "allocator". The instances of `HierarchicalAllocatorProcess` launched in the same instance of libprocess after that will be assigned IDs like "allocator(2)", "allocator(3)" and so on. Previously, to query an HTTP endpoint exposed by the allocator, the user had to figure out the allocator process id and use it to build the URL (like "https://localhost:5050/hierarchical_allocator(1)/..."); now, the allocator debugging endpoints are accessible via fixed URLs like "https://localhost:5050/allocator/offer_constraints_debug". Review: https://reviews.apache.org/r/72887
Apache Mesos is a cluster manager that provides efficient resource isolation and sharing across distributed applications, or frameworks. It can run Hadoop, Jenkins, Spark, Aurora, and other frameworks on a dynamically shared pool of nodes.
Visit us at mesos.apache.org.
Documentation is available in the docs/ directory. Additionally, a rendered HTML version can be found on the Mesos website's Documentation page.
Instructions are included on the Getting Started page.
Apache Mesos is licensed under the Apache License, Version 2.0.
For additional information, see the LICENSE and NOTICE files.