Apache YuniKorn Core

Clone this repo:
  1. 361d455 [YUNIKORN-476] placeholder allocation and swap (#236) by Wilfred Spiegelenburg · 4 days ago master
  2. dcf631d [YUNIKORN-499] race condition in sorting apps (#234) by Wilfred Spiegelenburg · 12 days ago
  3. 5471d84 [YUNIKORN-494]Rename the AllocationRelease Request and Response in core (#232) by Ting-Yao Huang · 4 weeks ago
  4. a1677dc [YUNIKORN-465] scheduler health check REST API (#222) by Kinga Marton · 5 weeks ago
  5. 01f5288 [YUNIKORN-480] root queue max resource update (#227) by Wilfred Spiegelenburg · 5 weeks ago

Apache YuniKorn (Incubating) - A Universal Scheduler

Build Status codecov Go Report Card License Repo Size

Apache YuniKorn (Incubating) is a light-weight, universal resource scheduler for container orchestrator systems. It is created to achieve fine-grained resource sharing for various workloads efficiently on a large scale, multi-tenant, and cloud-native environment. YuniKorn brings a unified, cross-platform, scheduling experience for mixed workloads that consist of stateless batch workloads and stateful services.

YuniKorn now supports K8s and can be deployed as a custom K8s scheduler. YuniKorn's architecture design also allows adding different shim layer and adopt to different ResourceManager implementation including Apache Hadoop YARN, or any other systems.

Get Started

See how to get started with running YuniKorn on Kubernetes, please read the documentation on yunikorn.apache.org.

Want to know more about the value of the YuniKorn project, and what YuniKorn can do? Here is some session recordings and demos.

Get Involved

Please read get involved document if you want to discuss issues, contribute your ideas, explore use cases, or participate the development.

If you want to contribute code to this repo, please read the developer doc. All the design docs are available here.

Code Structure

Apache YuniKorn (Incubating) project has the following git repositories:

The yunikorn-core is the brain of the scheduler, which makes placement decisions (allocate container X on node Y) according to the builtin rich scheduling policies. Scheduler core implementation is agnostic to the underneath resource manager system.