You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (Jira)" <ji...@apache.org> on 2021/05/20 20:40:00 UTC
[jira] [Assigned] (GEODE-9295) entry idle expiration threads may
hang
[ https://issues.apache.org/jira/browse/GEODE-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider reassigned GEODE-9295:
---------------------------------------
Assignee: Darrel Schneider
> entry idle expiration threads may hang
> --------------------------------------
>
> Key: GEODE-9295
> URL: https://issues.apache.org/jira/browse/GEODE-9295
> Project: Geode
> Issue Type: Bug
> Components: expiration
> Affects Versions: 1.13.0, 1.13.1, 1.13.2, 1.13.3, 1.14.0, 1.15.0
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
>
> GEODE-7921 in 1.13 introduced this issue. When processing a message used by entry idle expiration to find out when an entry was last accessed on any member of the cluster it now checks for a null cache, region, and entry. If any of them are null the message simply returns. The problem is that the expiration thread that sent this message waits forever for a reply. So unless the member that found a null leaves the cluster, the expiration thread will be hung waiting for a reply that will never be sent.
> The fix for this is easy. We just need to send a reply of zero when we find a null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)