[ 
https://issues.apache.org/jira/browse/YARN-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allen Wittenauer updated YARN-357:
----------------------------------
    Fix Version/s:     (was: 3.0.0)

> App submission should not be synchronized
> -----------------------------------------
>
>                 Key: YARN-357
>                 URL: https://issues.apache.org/jira/browse/YARN-357
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 0.23.3, 3.0.0, 2.0.0-alpha
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For: 2.0.3-alpha, 0.23.7
>
>         Attachments: YARN-357.branch-23.patch, YARN-357.patch, 
> YARN-357.patch, YARN-357.txt
>
>
> MAPREDUCE-2953 fixed a race condition with querying of app status by making 
> {{RMClientService#submitApplication}} synchronously invoke 
> {{RMAppManager#submitApplication}}. However, the {{synchronized}} keyword was 
> also added to {{RMAppManager#submitApplication}} with the comment:
> bq. I made the submitApplication synchronized to keep it consistent with the 
> other routines in RMAppManager although I do not believe it needs it since 
> the rmapp datastructure is already a concurrentMap and I don't see anything 
> else that would be an issue.
> It's been observed that app submission latency is being unnecessarily 
> impacted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to