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/05/11 01:22:12 UTC
[jira] [Updated] (YARN-4987) Read cache concurrency issue between
read and evict in EntityGroupFS timeline store
[ https://issues.apache.org/jira/browse/YARN-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Li Lu updated YARN-4987:
------------------------
Attachment: YARN-4987-trunk.001.patch
Upload a patch to add reference counting mechanism to fix the concurrency issue.
> Read cache concurrency issue between read and evict in EntityGroupFS timeline store
> ------------------------------------------------------------------------------------
>
> 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
> Attachments: YARN-4987-trunk.001.patch
>
>
> To handle concurrency issues, key value based timeline storage may return null on reads that are concurrent to service stop. This is actually caused by a concurrency issue between cache reads and evicts. Specifically, if the storage is being read when it gets evicted, the storage may turn into null. EntityGroupFS timeline store needs to handle this case gracefully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org