You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2022/06/15 17:59:00 UTC
[jira] [Resolved] (GEODE-10380) When dispatcher socket buffer is full, the ReAuth won't get sent to the client causing a deadlock
[ https://issues.apache.org/jira/browse/GEODE-10380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jinmei Liao resolved GEODE-10380.
---------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
> When dispatcher socket buffer is full, the ReAuth won't get sent to the client causing a deadlock
> -------------------------------------------------------------------------------------------------
>
> Key: GEODE-10380
> URL: https://issues.apache.org/jira/browse/GEODE-10380
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Affects Versions: 1.15.0
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Priority: Major
> Labels: needsTriage, pull-request-available
> Fix For: 1.15.0
>
> Attachments: Screen Shot 2022-06-14 at 5.37.18 PM.png
>
>
> # message dispatcher trying to send a reAuth message to the client, but not able to because the socket buffer is full.
> # client updater is blocked waiting for a regionEntry lock when doing a remove operation.
> # the regionEntry lock is held by a client operation doing destroy on that same key
> # the client operation is waiting for the re_auth op to finish.
> # the re_auth command on the server is blocked by the #1 holding the lock
--
This message was sent by Atlassian Jira
(v8.20.7#820007)