You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/12/07 17:52:58 UTC
[jira] [Commented] (GEODE-2182) Possible race condition when
estimating index size and an entry is destroyed
[ https://issues.apache.org/jira/browse/GEODE-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729383#comment-15729383 ]
ASF subversion and git services commented on GEODE-2182:
--------------------------------------------------------
Commit c2b1c8b1c172073824a8e5c48c45a4285f15e6b1 in geode's branch refs/heads/develop from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c2b1c8b ]
GEODE-2182: try-catch around size estimation for index look ups
* Fix possible race condition where entry is destroyed
> Possible race condition when estimating index size and an entry is destroyed
> ----------------------------------------------------------------------------
>
> Key: GEODE-2182
> URL: https://issues.apache.org/jira/browse/GEODE-2182
> Project: Geode
> Issue Type: Bug
> Reporter: Jason Huynh
> Assignee: Jason Huynh
>
> There is a possible race condition when estimating size of an index and an entry is destroyed. This doesnt get caught and instead percolates to the top as an EntryDestroyedException.
> A quick work around would be to catch the exception and return 0, this may lead to an inefficient lookup but the results would be correct.
> The better alternative would be to continue iterating if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)