Hey folks,

We have some new streaming use cases with Apache Flink that could
potentially leverage YuniKorn for resource scheduling.

The initial implementation is to use K8s namespace for resource quota
management. We are investigating what could be some strong benefits
switching to YuniKorn in streaming cases for long-running services. For
example: Job queueing, job ordering, resource reservation, user groups etc
all seem to be more desirable for batch use cases.

Any thoughts or suggestions?

Thanks,
Chenya

Reply via email to