You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Chen Yu Teng (Jira)" <ji...@apache.org> on 2021/08/02 05:45:00 UTC
[jira] [Created] (YUNIKORN-772) Add AllocationAskUpdate in
message:UpdateRequest
Chen Yu Teng created YUNIKORN-772:
-------------------------------------
Summary: Add AllocationAskUpdate in message:UpdateRequest
Key: YUNIKORN-772
URL: https://issues.apache.org/jira/browse/YUNIKORN-772
Project: Apache YuniKorn
Issue Type: Improvement
Components: scheduler-interface
Reporter: Chen Yu Teng
Fix For: 1.0.0
Attachments: description.png
Description
When resource requirement changes in pod phase, shim will update locally and core-scheduler doesn't know it.
Web and core-scheduler shows resource requirement changed when pod phase transited from initialization to running state
Any case?
This situation happens in YUNIKORN-706 .
Core-scheduler creates allocationAsk which is stable and calculated from containers.
If initcontainer resource requirements replace some containers requirements, core-scheduler will create allocationAsk and see it as fixed allocation and ignore resource requirement changed when pod phase transited from initialization to running state.
!description.png|width=693,height=328!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org