[jira] [Created] (YUNIKORN-1628) YuniKorn application traceability

["Peter Bacsko (Jira)" <ji...@apache.org>]

Peter Bacsko created YUNIKORN-1628:
--------------------------------------

             Summary: YuniKorn application traceability
                 Key: YUNIKORN-1628
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1628
             Project: Apache YuniKorn
          Issue Type: New Feature
          Components: core - scheduler
            Reporter: Peter Bacsko


The current implementation of YuniKorn is focused on the application and the states of the application. K8s does not and cannot provide details on what happens inside the application. This limits what we can offer at a YuniKorn level for applications.

To increase supportability, we need to understand what happens inside the core scheduler and how we got into a certain state.

We want to record a stream of events in memory when something relevant happens which is related to the application or nodes:
* Partition changed (nodes added / removed, capacity changed, etc.)
* Application created / removed
* An ask is created / removed
* An allocation is created / removed
* Reservation occurs
* Placeholder is replaced
* etc.

The recorded events should be queried from the REST interface.

The number of stored events can be limited by two settings: maximum number of events or expiration time (eg. events from the past 5 minutes).




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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