[SGF-226] Support for requesting a peer member's configuration from a GemFire Locator/Manager using the new Cluster-based Configuration Service. Created: 13/Nov/13  Updated: 23/Feb/15  Resolved: 23/Feb/15

Status: Closed
Project: Spring Data GemFire
Component/s: None
Affects Version/s: None
Fix Version/s: 1.5 RC1 (Evans), 1.6 M1 (Fowler)

Type: New Feature Priority: Major
Reporter: John Blum Assignee: John Blum
Resolution: Complete Votes: 0
Labels: GemFire, PersistentConfig, Spring
Remaining Estimate: 20d
Time Spent: Not Specified
Original Estimate: 20d
Environment:

Spring and GemFire 7.5 (Cedar)


Last updater: Trevor Marshall

 Description   

The GemFire 7.5 (Cedar) release will add the ability for new members to request and get it's configuration from a shared, persistent configuration service running in the GemFire Locator/Manager on startup.

This functionality and the basis of the implementation will be similar to Spring Data GemFire's existing support for native cache.xml, except in this case, a Spring Data GemFire configured member will make a network request to the Locator/Manager to get the cluster-wide, persisted and shared configuration instead.



 Comments   
Comment by John Blum [ 12/Aug/14 ]

Committed to 'master' in revisions f427125, 6cb2301 and 65b0793 for SDG 1.5.0.RC1 in the Spring Data Evans release train.

Generated at Tue Feb 25 19:29:09 UTC 2020 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.