Odg: Add new attribute to count members visible to member

[Mario Kevo]

Hi,

Just a reminder of this question.

BR,
Mario

Šalje: Mario Kevo
Poslano: 23. lipnja 2021. 13:15
Prima: dev@geode.apache.org 
Predmet: Add new attribute to count members visible to member

Hi, devs,

I'm trying to fix attribute visibleNodes in MemberMXBean as for me it seems 
that we don't have a correct value for it. (More description in the ticket 
GEODE-9101<https://issues.apache.org/jira/browse/GEODE-9101>)
The ticket is opened and PR#6225<https://github.com/apache/geode/pull/6225> is 
created.

The earliest version of GemFire had locators which were not members (ie not 
nodes), but locators now are definitely members (ie nodes). The next type of 
locators in GemFire were members (ie nodes) but without caches. As of GemFire 
7.0, all locators also have a cache. So in every version of Geode, all locators 
are members with caches. The methods to create that earliest type of locator 
still exists but is deprecated... so deprecated internal methods are now the 
only way to create the thin locators that are not peer-to-peer members of the 
cluster.

Not sure if we should change the existing attribute as it is done in the PR, or 
we need to keep this attribute and add a new attribute something like 
visibleMembers which will count all members in the system visible to one of the 
members?

Thanks and BR,
Mario

Add new attribute to count members visible to member

[Mario Kevo]

Hi, devs,

I'm trying to fix attribute visibleNodes in MemberMXBean as for me it seems 
that we don't have a correct value for it. (More description in the ticket 
GEODE-9101)
The ticket is opened and PR#6225 is 
created.

The earliest version of GemFire had locators which were not members (ie not 
nodes), but locators now are definitely members (ie nodes). The next type of 
locators in GemFire were members (ie nodes) but without caches. As of GemFire 
7.0, all locators also have a cache. So in every version of Geode, all locators 
are members with caches. The methods to create that earliest type of locator 
still exists but is deprecated... so deprecated internal methods are now the 
only way to create the thin locators that are not peer-to-peer members of the 
cluster.

Not sure if we should change the existing attribute as it is done in the PR, or 
we need to keep this attribute and add a new attribute something like 
visibleMembers which will count all members in the system visible to one of the 
members?

Thanks and BR,
Mario