[
https://issues.apache.org/jira/browse/YUNIKORN-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit closed YUNIKORN-1608.
----------------------------------
> Configuration updates and storage for limit
> --------------------------------------------
>
> Key: YUNIKORN-1608
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1608
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Qi Zhu
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> The configuration is read as part of the queue configuration. The queue
> configuration when processed creates, deletes or updates queues from the
> queue structure as appropriate. For limits linked to users or groups we could
> pre-generate the named entries but we cannot do that for wildcards. To
> support wildcards we need to at least store the configuration inside the user
> group manager code.
>
> The definition of the configuration store and the methods that need to be
> defined will be left as an implementation detail. It must be internal to the
> user group manager and will be based on the existing configuration objects.
>
> The configuration for the limits should be maintained as a separate hierarchy
> from the scheduling queues and the tracked users and groups. This is required
> to allow parallel processing of changes and scheduling. This becomes more
> important with an increased number of users, groups and or queues.
>
> Proposal is to pass the full configuration after it has been accepted by the
> system to an independent update routine for updating the affected objects in
> the user group manager.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
