[jira] [Commented] (YUNIKORN-1087) track scheduling time in the allocation

["Anuraag Nalluri (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502545#comment-17502545 ] 

Anuraag Nalluri commented on YUNIKORN-1087:
-------------------------------------------

[~wilfreds] How do you recommend this information should be surfaced in REST calls? Should we expose a path on routes.go [ex. /ws/v1/allocs] showing a list of current allocations? One of the newly added fields would be "createTime" (similar to AllocationAsk) and there could be a "elapsedTimeSinceAsk" as well. For replacement allocs, we can also have an "elapsedTimeSincePlaceholder".

Any guidance you can provide here would be greatly appreciated.

> track scheduling time in the allocation
> ---------------------------------------
>
>                 Key: YUNIKORN-1087
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1087
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Anuraag Nalluri
>            Priority: Major
>
> An allocation is based on the AllocationAsk which is based on the pod. We know the time the ask is created but we have no information on when the allocation was created based on that ask.
> The time delay between the two: from ask creation to allocation tells us how long it took the scheduler to find a location for the pod. Important detail to have during troubleshooting.
> We should also take into account placeholders and if/when they trigger a replacement and look at the times to track in the allocation.
> Details should be exposed in the REST objects.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org