geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jinmei Liao <jil...@pivotal.io>
Subject [Proposal]: behavior change when region doesn't exist in cluster configuration
Date Thu, 19 Apr 2018 21:58:20 GMT
Scenario:
a locator with cluster configuration enabled and a server started with a
cache.xml that has /regionA defined and connected to this locator. So the
initial state is the locator has an empty cluster configuration for the
cluster, but the server has a region defined in it's cache.

Old behavior:
when user execute "create index --region=/regionA ...." command using gfsh,
the index creation is successful on the server, and the server returns a
xml section that contains both <region> and <index> elements, CC is updated
with this xml, so the end result is: both region and index end up in the
cluster configuration.

Problem with old behavior:
Not sure if the region is a cluster wide configuration. What if a region
with the same name, but different type exists on different servers? the xml
returned by different server might be different.

New behavior:
when user execute "create index --region=/regionA ...." command using gfsh,
the index creation is successful on the server. We failed to find the
region in the existing cluster configuration, so cluster configuration will
NOT be updated.

I would also suggest that this would not apply to index alone, any element
inside region would have the same behavior change if we approve this.

Thanks!

-- 
Cheers

Jinmei

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message