You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2016/04/28 01:57:12 UTC

[jira] [Commented] (YARN-4987) EntityGroupFS timeline store needs to handle null storage gracefully

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

Li Lu commented on YARN-4987:
-----------------------------

I just notice there is a caching/concurrency bug hidden behind this issue. The cache item being reclaimed may actually be reading by some other concurrent readers. Will fix the problem in this JIRA. 

> EntityGroupFS timeline store needs to handle null storage gracefully
> --------------------------------------------------------------------
>
>                 Key: YARN-4987
>                 URL: https://issues.apache.org/jira/browse/YARN-4987
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Li Lu
>            Assignee: Li Lu
>            Priority: Critical
>
> To handle concurrency issues, key value based timeline storage may return null on reads that are concurrent to service stop. EntityGroupFS timeline store needs to handle this case gracefully. 



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