Thanks Kirk. This is for PR clear; I ended up registering/adding a new membership listener on DistributionManager (DM).
I was trying to take advantage of MembershipListener on PR region-advisor. It turns out that this gets called even before the view is updated on DM. -Anil On Fri, Apr 17, 2020 at 3:36 PM Kirk Lund <kl...@apache.org> wrote: > Any requirements for this to be a User API vs internal API? > > For internal APIs, you can register a MembershipListener on > DistributionManager -- at least one flavor of which returns a > Set<InternalDistributedMember> of current members which you could check > before relying on callbacks. > > On Fri, Apr 17, 2020 at 3:03 PM Anilkumar Gingade <aging...@pivotal.io> > wrote: > > > Is there a better way to know if a member has left the distributed > system, > > than following: > > I am checking using: > > "partitionedRegion.getDistributionManager().isCurrentMember(requester));" > > > > This returns true, even though the AdvisorListener on > > ParitionedRegion already processed memberDeparted() event. > > > > I want to know if a member has left after invoking the > membershipListener. > > > > -Anil. > > >
