I've been looking into the code a little bit to see if this is possible. I'm
not sure it is right now.
Here's some pointers at where to look at. Most of the magic is happening in
JGroupsMessenger. JGroupsMessenger wraps jgroups, which we are using to UDP
messaging related to membership.
The fi
> Is there any way to configure a bind address to be used only for membership?
To your first question, I asked around but I’m not aware of anything like what
you are looking for. What you are describing does seem like it could become a
common setup on Kubernetes, but I personally haven’t tried u
On Jan 20, 2021, at 10:36 AM, Owen Nichols
mailto:onich...@vmware.com>> wrote:
Sounds like good cleanup, but I'm not sure I understand why you propose
breaking up the work and sneaking it in through mostly-unrelated PRs? My first
thought would be do it in one shot, start by deleting the old
Sounds like good cleanup, but I'm not sure I understand why you propose
breaking up the work and sneaking it in through mostly-unrelated PRs? My first
thought would be do it in one shot, start by deleting the old constants, and
let the compiler guide you to all code that needs pruning. Or, if
Given the lack of objections to this proposal I have moved forward with some of
this proposal. In deeper investigation it has come to light that GFE_82 was
never used and appeared only as an artifact of open sourcing preparations. I
have therefore retargeted GFE_81 as the oldest ordinal version
It seems this is not a trendic topic... 🙂 Let me share my approach by the
moment, maybe this will receive more comments:
I thought that it will be interesting to take a look at how the membership
works (how the distributed system is created), to check if at some point I
could decouple how the v
