You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2020/06/25 08:10:00 UTC

[jira] [Resolved] (YUNIKORN-117) Create event cache for scheduling events

     [ https://issues.apache.org/jira/browse/YUNIKORN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg resolved YUNIKORN-117.
--------------------------------------------
    Fix Version/s: 0.9
       Resolution: Fixed

Changes committed, further improvements filed as new jiras

> Create event cache for scheduling 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
>             Fix For: 0.9
>
>
> 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: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org