TL;DR — YuniKorn is an Apache scheduler that replaces the default Kubernetes scheduler with one built for multi-tenant batch + service workloads. Its signature is hierarchical queues with elastic quotas and resource fairness, plus gang scheduling and preemption. Heritage in Big Data (Spark, Flink) makes it strong wherever data + ML share one cluster.
What it is
Apache YuniKorn is a universal, Kubernetes-native resource scheduler for big-data and ML workloads. Unlike add-ons that sit beside the default scheduler, YuniKorn is designed to be the scheduler — handling both long-running services and batch jobs through one policy engine. In the AI Native landscape it's in AI Native Infra › Orchestration and Scheduling.
Why it exists
The default scheduler has no concept of queues, tenants, or fairness — it places pods, full stop. Organizations running Spark, Flink, and ML training on shared clusters need org-chart-shaped resource control: department → team → project, each with guaranteed and burstable quota. YuniKorn brings the YARN-style hierarchical-queue model that Big Data teams expect, to Kubernetes.
How it works
YuniKorn is application-aware: it groups pods into apps and schedules apps against a queue hierarchy. Each queue has min (guaranteed) and max (cap) resources; unused capacity flows elastically to siblings, then is reclaimed via preemption when owners need it. It can run as the primary scheduler for all pods.
Fig 1 — Hierarchical queues: guaranteed + elastic quota cascading down the org tree.
Key features
- Hierarchical queues — nested queues with guaranteed/max quotas and elastic borrowing.
- Resource fairness — fair sharing across tenants and queues.
- Job ordering — FIFO or FAIR ordering within queues.
- Gang scheduling — schedule an app only when its minimum members fit; reduces fragmentation and can trigger proactive scale-up.
- Priority & preemption — higher-priority work reclaims resources.
- Universal — one scheduler for batch and services; pluggable node-sorting policies (e.g. bin-pack vs spread).
Quick start
Install via Helm; it can take over scheduling for the cluster (or just for pods you target):
helm repo add yunikorn https://apache.github.io/yunikorn-release
helm install yunikorn yunikorn/yunikorn -n yunikorn --create-namespace
kubectl get pods -n yunikorn # scheduler + admission controllerQueues and placement rules live in YuniKorn's config (a ConfigMap); apps land in a queue by annotation or placement rule, e.g. yunikorn.apache.org/queue: root.team-ml.training.
When to use, when to skip
Use it when you run mixed Big-Data + ML on shared Kubernetes and want YARN-style hierarchical fairness as the cluster's primary scheduler — especially Spark/Flink-heavy shops (it's common on EMR-on-EKS). One scheduler covering both batch and services is its big selling point.
Skip it if you only need gang scheduling for training (Volcano is more AI/HPC-focused) or just job queueing/quota layered on the default scheduler (Kueue is lighter and doesn't replace the scheduler).
vs the alternatives
| Tool | Best for | Trade-off |
|---|---|---|
| YuniKorn | Hierarchical queues, batch+service in one scheduler, Big Data | Replaces the scheduler; queue-first model |
| Volcano | AI/HPC gang scheduling + rich placement | More AI-specific, less queue hierarchy |
| Kueue | Quota/queueing on the default scheduler | Admission only |
References
- Apache YuniKorn — project site + docs.
- Gang scheduling — the model in detail.
- apache/yunikorn-core — source.
Extra reads
- Batch scheduling compared — YuniKorn vs Volcano vs Kueue.
- Spark on K8s with YuniKorn — gang scheduling in practice.
- YuniKorn for EMR on EKS — a production deployment.
Verified against the official Apache YuniKorn docs (yunikorn.apache.org), May 2026.
Where YuniKorn fits: the mental model
YuniKorn is a compute or serving layer that places expensive AI workloads and turns models into reliable runtime services. The useful question is not simply “can it run the demo?” It is whether the component gives your team a clear ownership boundary, predictable failure behavior, and enough evidence to operate changes safely. Treat it as one replaceable layer in a larger system rather than letting it quietly become the architecture.
Start by drawing the request and data path. Mark where untrusted input enters, where identity is checked, where durable state changes, and where retries can repeat work. That diagram tells you which guarantees belong to YuniKorn and which still belong to your application, platform, cloud provider, or database. The distinction matters during incidents: a healthy process is not proof that the end-to-end task is correct.
Core concepts you should understand first
The vocabulary below is more important than any single SDK method. It lets application engineers, platform engineers, security reviewers, and incident responders describe the same system without confusing a framework feature with an end-to-end guarantee.
| Concept | Meaning in this layer | Design question |
|---|---|---|
| Resource request | Capacity reserved for placement; inaccurate requests create pending work or stranded accelerators. | Write down how YuniKorn represents or enforces this before production. |
| Topology | NUMA, PCIe, NVLink, rack, and zone relationships that can dominate distributed workload performance. | Write down how YuniKorn represents or enforces this before production. |
| Batching | Combining requests or examples to improve accelerator utilization at the cost of queueing latency. | Write down how YuniKorn represents or enforces this before production. |
| Parallelism | Splitting model weights, pipeline stages, data, or requests across devices and processes. | Write down how YuniKorn represents or enforces this before production. |
| Preemption | Reclaiming resources from lower-priority work; safe jobs need checkpoint and resume semantics. | Write down how YuniKorn represents or enforces this before production. |
| Cold start | Time to schedule, pull images, load weights, compile kernels, and become ready. | Write down how YuniKorn represents or enforces this before production. |
From quick start to a production deployment
The earlier quick start proves that the package or service runs. Production readiness is a different exercise. Build the smallest vertical slice that crosses every real boundary—identity, network, persistence, upstream provider, telemetry, and rollback—before broadening the feature set.
- Pin the compatibility envelope. Record the YuniKorn release, language/runtime version, client SDK version, model or backend version, and—where applicable—Kubernetes API or driver requirements. Use a lock file, immutable image digest, or chart version; floating “latest” tags prevent repeatable rollback.
- Define contracts before configuration. Write the accepted input, successful output, error classes, timeout, idempotency behavior, and ownership of durable state. Validate at the boundary so corrupt work fails early instead of surfacing deep in a workflow.
- Create separate development, staging, and production identities. Do not copy a broad personal API key into every environment. Prefer workload identity or short-lived credentials, scope access by tenant and operation, and verify denial cases as part of deployment.
- Add bounded failure behavior. Every remote call needs a deadline. Retry only transient, idempotent operations with exponential backoff and jitter. Set concurrency and queue limits so an upstream slowdown becomes controlled backpressure rather than resource exhaustion.
- Instrument the complete path. Emit a correlation ID, component and release version, duration, outcome, retry count, and resource or cost dimensions. Keep sensitive prompt, document, and credential values out of ordinary logs.
- Ship through a reversible rollout. Run compatibility and regression tests, deploy to a canary or isolated workload, compare service-level indicators, then increase exposure. Preserve the previous artifact and configuration until rollback has been exercised.
Production configuration checklist
- Pin artifacts by version and, where possible, digest.
- Set connect, request, and total workflow deadlines.
- Bound retries, concurrency, queue length, and payload size.
- Separate read-only operations from mutations.
- Use idempotency keys for replayable mutations.
- Persist canonical state outside disposable workers.
- Encrypt traffic and durable data with managed keys.
- Redact secrets, tokens, prompts, and personal data.
- Apply per-tenant quotas and authorization filters.
- Expose readiness separately from process liveness.
- Back up metadata and test restore, not only backup.
- Document owner, escalation path, RPO, and RTO.
Failure modes and the response you should design
| Failure mode | What you observe | Engineering response |
|---|---|---|
| Unschedulable gang | Some workers start but the full distributed job cannot fit. | Use gang scheduling or admission so the group starts together. |
| Topology penalty | Workers span slow links or cross zones. | Express topology constraints and measure collective communication. |
| Memory fragmentation | Free memory exists but a large allocation fails. | Tune allocation/batching and recycle workers under controlled policy. |
| Driver mismatch | Host driver, runtime, CUDA, and framework are incompatible. | Qualify an immutable compatibility matrix before rollout. |
| Cold-start spike | Scale-out misses the latency objective. | Pre-pull images, cache weights, keep warm capacity, and measure each phase. |
| Noisy neighbor | One workload consumes shared network, CPU, or storage. | Apply quotas, priorities, isolation, and per-tenant saturation metrics. |
Turn these rows into runbook entries with an alert, first diagnostic query, safe mitigation, and escalation owner. Test at least one failure in staging every release cycle. If the system cannot be forced into a failure safely, it is usually not yet observable or isolated enough.
Security, privacy, and tenant isolation
Place YuniKorn in a threat model, not just an architecture diagram. Identify human users, workload identities, administrators, upstream services, model providers, artifact registries, and data stores. For each edge, document authentication, authorization, encryption, audit evidence, and the consequence of credential compromise.
Apply least privilege at the operation and resource level. A component that only retrieves documents should not be able to delete the index; an evaluation worker should not inherit production mutation credentials; a model-serving pod should not need cluster-admin. In multi-tenant systems, enforce the tenant boundary before retrieval or execution and include tenant identity in quotas and audit events. Never rely on a prompt instruction, namespace string supplied by the client, or UI filtering as authorization.
Decide what data is permitted in telemetry. Prompts, retrieved chunks, tool arguments, model responses, notebooks, and traces can contain secrets or regulated data. Redact close to collection, keep high-sensitivity payload capture opt-in, encrypt exports, restrict support access, and give each class an explicit retention period. Verify deletion across caches, replicas, indexes, backups, and derived evaluation datasets.
Observability and service-level objectives
A useful dashboard follows the user-visible unit of work and then decomposes it by component, release, tenant tier, backend, and failure class. Start with these signals for YuniKorn:
- accelerator utilization and memory — graph both rate and distribution, then compare with the previous release and traffic mix.
- queue wait and pending duration — graph both rate and distribution, then compare with the previous release and traffic mix.
- time to first token or first result — graph both rate and distribution, then compare with the previous release and traffic mix.
- throughput per device — graph both rate and distribution, then compare with the previous release and traffic mix.
- cold-start and model-load time — graph both rate and distribution, then compare with the previous release and traffic mix.
- failure, eviction, and preemption rate — graph both rate and distribution, then compare with the previous release and traffic mix.
Choose an SLO at the boundary your users experience, such as “99% of accepted tasks complete correctly within five minutes over 28 days.” Availability alone is insufficient for AI systems because a fast but incorrect or ungrounded result is still a failure. Pair latency and completion objectives with a reviewed quality or policy indicator. Page on rapid error-budget burn; use tickets for slow capacity trends.
Testing and release strategy
Use four layers. Unit tests cover deterministic adapters, schemas, policy, and error mapping without a live external service. Contract tests exercise the pinned integration boundary—API, CLI, SDK, protocol, or ephemeral service—and verify its exact surface. Scenario tests exercise representative end-to-end cases, including permissions and state. Load and resilience tests establish saturation, queue behavior, retry amplification, and recovery after dependency loss.
Keep a small blocking suite for every commit and a broader scheduled suite for expensive or probabilistic checks. Store results with the application version, YuniKorn version, configuration hash, model/backend version, dataset version, and random seed. A score without that provenance cannot explain a regression. Before upgrading, read the migration notes, run both versions against the same replay set, and explicitly test rollback across any schema or state transition.
How to decide whether YuniKorn is the right tool
| Question | Evidence to collect | Red flag |
|---|---|---|
| Does it remove a real constraint? | A measured bottleneck, missing guarantee, or repeated custom component. | Adoption is based only on a demo or feature count. |
| Can the team operate it? | Named owner, upgrade path, alerts, runbooks, backup, restore, and on-call skills. | Only the original prototype author understands failure behavior. |
| Is the interface portable? | Your domain contracts wrap vendor-specific APIs; data and state have an export path. | Business objects are inseparable from framework internals. |
| Does it meet the envelope? | Benchmarks using your payloads, concurrency, topology, quality bar, and cost model. | Published benchmark hardware or workload does not resemble production. |
| Is failure affordable? | Tested degraded mode, bounded blast radius, rollback, RPO, and RTO. | A component outage blocks unrelated tenants or irreversible actions. |
Prefer the smallest component that satisfies the required guarantees. A provider SDK, relational table, background job, or standard Kubernetes controller is often better than another platform when the workload is small and predictable. Choose YuniKorn when its specific abstraction removes sustained engineering work and the team is willing to own its lifecycle.
A focused 90-minute validation lab
- Minutes 0–15: run the documented quick start in a disposable environment with pinned dependencies. Save the exact commands and a known-good input/output fixture.
- Minutes 15–35: replace the toy input with one representative case from your system. Add schema validation, a deadline, and a correlation ID.
- Minutes 35–55: force invalid credentials, a timeout, malformed input, and one dependency failure. Record the observed errors and whether retries are safe.
- Minutes 55–75: run a small concurrency test and capture latency, throughput, saturation, and unit cost. Do not extrapolate beyond the tested range.
- Minutes 75–90: write the adoption decision: required guarantees met, open risks, owner, next experiment, and the simplest credible alternative.
Frequently asked questions
Should we standardize on YuniKorn for every team?
Standardize the contracts, telemetry, security controls, and release evidence first. Standardizing one implementation is useful only when workloads share requirements and a platform team owns upgrades and support.
Can we use the hosted version and skip operations work?
Hosted service removes part of the control-plane burden, not architecture ownership. You still own identity, tenant isolation, data classification, quotas, dependency failure, observability, export, and an exit plan.
What should be pinned for reproducibility?
Pin the tool/server, client SDK, runtime, configuration, model or backend, container image digest, and test dataset. Record these values with every benchmark and evaluation result.
When is a proof of concept ready for production?
After representative success and failure tests pass, sensitive data paths are approved, limits and SLOs are defined, telemetry and runbooks exist, restore or rollback is rehearsed, and an accountable owner accepts the remaining risk.
Official sources and freshness
This guide was reviewed for architecture and operational guidance on 10 July 2026. Projects evolve quickly: verify installation syntax, supported versions, feature maturity, and upgrade notes against the exact release you deploy.