hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.
Date Tue, 23 Jul 2013 15:08:48 GMT

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

Jason Lowe updated YARN-573:
----------------------------

    Priority: Critical  (was: Major)

Bumping the priority.  We have seen an instance of the PublicLocalizer looping incessantly
in HashMap.put, usually a tell-tale sign of corruption via multithreaded, unsynchronized accesses
to HashMap.  When this occurred, the public localizer became stuck and all task attempts with
public files in the distributed cache failed to launch due to task timeouts.
                
> Shared data structures in Public Localizer and Private Localizer are not Thread safe.
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-573
>                 URL: https://issues.apache.org/jira/browse/YARN-573
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
>            Priority: Critical
>
> PublicLocalizer
> 1) pending accessed by addResource (part of event handling) and run method (as a part
of PublicLocalizer.run() ).
> PrivateLocalizer
> 1) pending accessed by addResource (part of event handling) and findNextResource (i.remove()).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message