[
https://issues.apache.org/jira/browse/YUNIKORN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117876#comment-17117876
]
Adam Antal commented on YUNIKORN-117:
-------------------------------------
Fine-tuned a bit in the message the store side in the core.
Latest output:
{noformat}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduling 52s yunikorn
default/task2 is queued and waiting for allocation
Normal PodUnscheduable 49s yunikorn Task
default/task2 state changes to Unscheduable
Warning InsufficientQueueResources 48s (x21 over 51s) yunikorn
Application application-sleep-0003 does not fit in root.default queue: Resource
0 vcore is lower than 1000
Warning InsufficientQueueResources 48s (x2 over 49s) yunikorn
Application application-sleep-0003 does not fit in root.default queue: Resource
0 memory is lower than 1000
{noformat}
I saw some data races, and strangely after some point no new events are emitted
into k8s. Will look into this tomorrow.
Updated core and shim drafts with the new implementations.
> Create event cache for queue and application events
> ---------------------------------------------------
>
> Key: YUNIKORN-117
> URL: https://issues.apache.org/jira/browse/YUNIKORN-117
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - cache, core - scheduler
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Critical
> Labels: pull-request-available
>
> Create a simple preliminary implementation of the event cache of YUNIKORN-42.
> We have the following limited scope for this task:
> - implement it as a separate process from the scheduler (similar to
> {{PartitionManager}})
> - only deal with queues and applications (the pods and nodes can be added
> later)
> - only store the apps last visited time from the scheduler
> - clean up those objects that haven't been visited in the last 24h
> Other cache implementations can be also considered.
> As a starting point, channels are a safe choice to have async communication
> with the scheduler without expecting bigger performance loss.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
