hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6840) Leverage RMStateStore to store scheduler configuration updates
Date Thu, 20 Jul 2017 00:34:00 GMT

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

Naganarasimha G R commented on YARN-6840:

bq. 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). 
So your estimation of 10kb is for each queue update? In between do we plan to store the hierarchy
as zookeeper nodes or whole queue configuration under a single node. In either case, we generally
tend to see 400 ~ 500 queues with our customers and expect much more to grow, would it be
of any concern ? 

> 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

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

View raw message