[jira] [Commented] (YUNIKORN-457) Find a way to pass the RMID to the webservice

["Kinga Marton (Jira)" <ji...@apache.org>]

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

Kinga Marton commented on YUNIKORN-457:
---------------------------------------

Today I thought a bit about how we can solve this issue and I found a better way to solve it, than the actual implementation:
 - When calling {{updateSchedulerConfig}} from the webservice, pass an empty RMID
 - In the {{updateSchedulerConfig}} if the RMID is empty, while processing the partitions, the clusterContext has a map with the partitions where the key is in the form of {{[rmID]partitionName}}. We can iterate through the partitions and check if in the map is a key having the partitionName from the changed config. If yes, then we can extract the rmID from the value stored in the clusterContext's partition map.
 - If the partition is a new one, use a default RMID, what we can store in the ClusterContext and set it when the first RM is registered.

> Find a way to pass the RMID to the webservice
> ---------------------------------------------
>
>                 Key: YUNIKORN-457
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-457
>             Project: Apache YuniKorn
>          Issue Type: Bug
>            Reporter: Kinga Marton
>            Assignee: Kinga Marton
>            Priority: Major
>
> When updating the configuration through the REST API, we need an RMId to reflect the changes in the configmap as well. With the actual approach this might not work properly if we would have more than one RM registered, or if we don't have any RM's.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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