Timothy Potter created YUNIKORN-2020:
----------------------------------------
Summary: Yunikorn aware of EBS volume attach limit per node
Key: YUNIKORN-2020
URL: https://issues.apache.org/jira/browse/YUNIKORN-2020
Project: Apache YuniKorn
Issue Type: Bug
Components: shim - kubernetes
Affects Versions: 1.3.0
Environment: AWS EKS 1.24
Reporter: Timothy Potter
Yunikorn attempts to schedule pods with EBS PV on node beyond the EBS volume
attach limit for that node.
I have my EBS CSI driver attach limit set to 23, but when I schedule pods via
Yunikorn, it schedules too many pods on the same node after the limit is
reached.
For example, I have a test STS that requests 30 pods with PVC. With Yunikorn, I
get 25 scheduled (vs. the 23 max limit I configured, not sure if that's a bug
in EBS CSI driver) and the last pod is stuck in {{ContainerCreating}} state.
{code}
Warning FailedAttachVolume 2m42s (x40 over 68m) attachdetach-controller
AttachVolume.Attach failed for volume
"pvc-be15c348-905d-4c7d-95d3-cffb2cb893ee" : rpc error: code = Internal desc =
Could not attach volume "vol-0fb6f7656a825c6f0" to node "XYZ": attachment of
disk "vol-0fb6f7656a825c6f0" failed, expected device to be attached but was
attaching
{code}
If I try to schedule the same test STS using the default scheduler, it
schedules all 30 pods but across 2 nodes as expected.
How can we configure Yunikorn to recognize / respect this EBS vol attach limit?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
