[jira] [Commented] (YARN-11174) Setting user limit factor on dynamic queues at runtime does not propagate to ConfigurationProperties

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on YARN-11174:
---------------------------------------

szilard-nemeth commented on PR #4443:
URL: https://github.com/apache/hadoop/pull/4443#issuecomment-1269715863

   Hi @9uapaw ,
   I can see that the jira YARN-11174 is resolved as a duplicate.
   Should we do the same with this PR? 
   
   Thanks.




> Setting user limit factor on dynamic queues at runtime does not propagate to ConfigurationProperties
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-11174
>                 URL: https://issues.apache.org/jira/browse/YARN-11174
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: András Győri
>            Assignee: András Győri
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> YARN-10838 introduced a ConfigurationProperties class, that is optimised for fast prefixed retrievals. However, changes at runtime on a CSConfig object will not have effect on this cache. The only way to propagate those changes is to reinitialise the entire cache, which could be costly. 
> In order to avoid unnecessary operations, we need a way to add new entries to the ConfigurationProperties in constant time.
> In addition to this, YARN-11006 implemented a way for dynamic queues to be able to override user limit factors via templates. However, this only worked because of the missing propagations, hence it is a bug in the logic that should be fixed.



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

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