You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce J Schuchardt (Jira)" <ji...@apache.org> on 2019/12/19 18:46:00 UTC
[jira] [Updated] (GEODE-7038) After auto-reconnect a server's
multicat communications aren't working correctly
[ https://issues.apache.org/jira/browse/GEODE-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce J Schuchardt updated GEODE-7038:
--------------------------------------
Fix Version/s: 1.11.0
> After auto-reconnect a server's multicat communications aren't working correctly
> --------------------------------------------------------------------------------
>
> Key: GEODE-7038
> URL: https://issues.apache.org/jira/browse/GEODE-7038
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This was observed in an server having multicast enabled on a Region. The server went into a GC pause and was kicked out of the cluster. After auto-reconnecting all of the servers were requested to shut down and they all hung on destroy-region message responses. Statistics showed constant multicast retransmission requests but no retransmissions being sent.
> When a Region is configured to use multicast all of its cache operation messages are multicast, including a destroy-region message.
> Some time ago we decided to stop sending Join Request Responses during discovery. These messages were responsible for carrying the JGroups multicast message digest so that a joining member could install this digest into its multicast protocol. Today these messages are only sent if a UDP Diffie-Hellman algorithm has been specified. We need to also ensure that we send these messages if multicast is enabled.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)