Enterprise DNA
O Open Source Observability medium

Yunikorn

by Community

Apache YuniKorn Core

Y

OSS

Yunikorn

Added 1 June 2026

#apache-yarn #go #kubernetes #universal-resource-scheduler #yunikorn

Overview

YuniKorn is a resource scheduler for Apache Hadoop YARN and Kubernetes that optimizes cluster utilization and job throughput. It uses a hierarchical queue model with fairness and preemption policies to allocate resources across multi-tenant environments.

Best for

Best for
Platform teams managing large, multi-tenant Hadoop or Kubernetes clusters needing advanced scheduling and fairness.

Use cases

  • Scheduling batch and streaming workloads on shared Kubernetes clusters
  • Enforcing resource quotas and fairness across teams or departments
  • Replacing default Kubernetes scheduler for large-scale, multi-tenant deployments

Notes

YuniKorn is a resource scheduler for Apache Hadoop YARN and Kubernetes that optimizes cluster utilization and job throughput. It uses a hierarchical queue model with fairness and preemption policies to allocate resources across multi-tenant environments.

1,014 stars on GitHub. Last updated 2026-05-29. Licensed Apache-2.0.

Use cases

  • Scheduling batch and streaming workloads on shared Kubernetes clusters
  • Enforcing resource quotas and fairness across teams or departments
  • Replacing default Kubernetes scheduler for large-scale, multi-tenant deployments

Pros

  • Supports both YARN and Kubernetes, enabling hybrid scheduling
  • Hierarchical queues provide fine-grained resource governance
  • Active community with Apache governance and open source codebase

Cons

  • Setup and configuration can be complex for smaller clusters
  • Documentation is sparse and assumes familiarity with YARN scheduling
  • Limited integration with non-Hadoop ecosystems

Indexed from awesome-llmops and enriched against its public facts.

Pros

  • Supports both YARN and Kubernetes, enabling hybrid scheduling
  • Hierarchical queues provide fine-grained resource governance
  • Active community with Apache governance and open source codebase

Cons

  • Setup and configuration can be complex for smaller clusters
  • Documentation is sparse and assumes familiarity with YARN scheduling
  • Limited integration with non-Hadoop ecosystems