I'll think about it a bit Greg. One of the main goals was to have the
membership system behave exactly the same as in GemFire, so I'm not sure
there's a lot to talk about. We only removed multicast discovery
because it was little-used and not well-tested.
I wouldn't refer to this work as the "new JGroups" because it isn't
based on JGroups anymore. All of the membership services are brand new
and called "GMS" for Group Membership Services. The only component in
the whole system that now refers to any JGroups code is the Messenger,
which uses it for reliable UDP messaging. Geode membership isn't based
on JGroups membership anymore, though there is a mapping between the two.
Le 11/20/2015 1:35 PM, Greg Chase a écrit :
Bruce - would you be willing to do an extended discussion in a near future
Geode Clubhouse: how Geode now behaves with the new JGroups and also new future
opportunities for features based on the revision?
If so, how much time would you need to cover this? A demo is not necessary
unless you have one on hand or are so inspired to create one.
This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and
autocorrect on my iPhone.
On Nov 20, 2015, at 1:22 PM, Bruce Schuchardt <bschucha...@pivotal.io> wrote:
The feature/GEODE-77 branch is now dead. I'll delete it in a few days if we're
satisfied with the merge.
Thank you to everyone who helped with this project or helped offload work from
people focusing on it. That includes quite a few of you who are reading this!
I want to remind everyone that there is now no multicast discovery in GEODE. You must
now use a Locator service as part of your distributed system. Multicast communications
can still be used by setting a multicast port and address, but multicast is no longer an
option for startup "discovery".
