[
https://issues.apache.org/jira/browse/YUNIKORN-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401977#comment-17401977
]
Wilfred Spiegelenburg commented on YUNIKORN-704:
------------------------------------------------
{quote}what you are describing here is like what we want to do with the
additional placement constraint, that was part of the interface design, but not
implemented today.
{quote}
That is not what I referenced. Instead of passing in a true/false for
unschedulable info in the Ask pass the node name. Leverage that name to place
it. We do no need the full set of placement constraints. We only want/need to
have this for the daemon set pods to be placed on an unschedulable node.
We're not implementing a full blown replacement for predicates. We just want to
align with the behavioural change that is part of the current K8s releases.
> [Umbrella] Use the same mechanism to schedule daemon set pods as the default
> scheduler
> --------------------------------------------------------------------------------------
>
> Key: YUNIKORN-704
> URL: https://issues.apache.org/jira/browse/YUNIKORN-704
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Chaoran Yu
> Assignee: Ting Yao,Huang
> Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: fluent-bit-describe.yaml, fluent-bit.yaml
>
>
> We sometimes see DaemonSet pods fail to be scheduled. Please see attached
> files for the YAML and _kubectl describe_ output of one such pod. We
> originally suspected [node
> reservation|https://github.com/apache/incubator-yunikorn-core/blob/v0.10.0/pkg/scheduler/context.go#L41]
> was to blame. But even after setting the DISABLE_RESERVATION environment
> variable to true, we still see such scheduling failures. The issue is
> especially severe when K8s nodes have disk pressure that causes lots of pods
> to be evicted. Newly created pods will stay in pending forever. We have to
> temporarily uninstall YuniKorn and let the default scheduler do the
> scheduling for these pods.
> This issue is critical because lots of important pods belong to a DaemonSet,
> such as Fluent Bit, a common logging solution. This is probably the last
> remaining roadblock for us to have the confidence to have YuniKorn entirely
> replace the default scheduler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
