Yes, the group membership service has been completely rewritten to use
off-the-shelf JGroups, so our join/leave, authentication and failure
detection are no longer performed by JGroups and use different messages
than the old GMS. UDP messages and membership identifiers have also
changed since JGroups on-wire message format has changed and JGroups has
moved to a UID-based identifier.
Le 5/11/2016 à 6:18 AM, Anthony Baker a écrit :
In this case, it definitely does not work due the changes we’ve made
in the Group Membership Service in geode.
Anthony
On May 11, 2016, at 12:10 AM, Greg Chase <[email protected]
<mailto:[email protected]>> wrote:
I would not attempt that simply because there is no guarantee of
compatibility between Geode, any release, and GemFire 8.x.
If it works, its not by design, and can't be counted on.
On Wed, May 11, 2016 at 12:07 AM, Gal Palmery <[email protected]
<mailto:[email protected]>> wrote:
Hi everybody,
Is it possible for geode to work partly with gemfire 8.2.0.5 on
the same grid?
Meaning – if some of the servers are running with gemfire 8.2.0.5
jars, and others running with geode M2 release version, will all
the servers be able to communicate correctly?
Thanks,
Gal
This message and the information contained herein is proprietary
and confidential and subject to the Amdocs policy statement, you
may review at http://www.amdocs.com/email_disclaimer.asp
