[
https://issues.apache.org/jira/browse/YARN-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092636#comment-16092636
]
Wangda Tan commented on YARN-6840:
----------------------------------
[[email protected]], thanks for your comments. To me, scheduler
configuration updates are not general data store. Diff of config update should
be small, and we can compress it before store, I expect less than 10KBs for
each update for very bad cases (after compression). And frequency of config
update will be much slower than application information.
So if we continue store states of application to RMStateStore, I didn't see any
issue of store configs to RMStateStore. Please let me know if you think
different.
> Leverage RMStateStore to store scheduler configuration updates
> --------------------------------------------------------------
>
> Key: YARN-6840
> URL: https://issues.apache.org/jira/browse/YARN-6840
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
>
> With this change, user doesn't have to setup separate storage system (like
> LevelDB) to store updates of scheduler configs. And dynamic queue can be used
> when RM HA is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
