[
https://issues.apache.org/jira/browse/YARN-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129262#comment-16129262
]
Jonathan Hung edited comment on YARN-5951 at 8/16/17 6:49 PM:
--------------------------------------------------------------
Hi [~yangjiandan], I wasn't able to repro #1 but it seems it's because the
synchronization in MutableCSConfigurationProvider causes the pending mutation
list to always be no more than size 1. So we should still fix the fact that the
pendingMutations list is modified mid-iteration.
For #2, you're right.
Filed YARN-7024 for these issues. Thanks for catching these!
was (Author: jhung):
Hi [~yangjiandan], I wasn't able to repro #1 but it seems it's because the
synchronization in MutableCSConfigurationProvider causes the pending mutation
list to always be no more than size 1. So we should still fix the fact that the
pendingMutations list is modified mid-iteration.
For #2, you're right.
Filed YARN-7024 for these issues.
> Changes to allow CapacityScheduler to use configuration store
> -------------------------------------------------------------
>
> Key: YARN-5951
> URL: https://issues.apache.org/jira/browse/YARN-5951
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jonathan Hung
> Assignee: Jonathan Hung
> Fix For: YARN-5734
>
> Attachments: YARN-5951-YARN-5734.001.patch,
> YARN-5951-YARN-5734.002.patch, YARN-5951-YARN-5734.003.patch,
> YARN-5951-YARN-5734.004.patch
>
>
> EDIT: changing this ticket. Found that the CapacityStoreConfigurationProvider
> is not necessary, since we can just grab a Configuration object from
> StoreConfigurationProvider with type "SCHEDULER" and create a
> CapacitySchedulerConfiguration from it.
> This ticket will track changes needed for integrating other components to be
> used by the capacity scheduler.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
