Ashish,
The keySetOnServer call is just an example of doing something on the server.
In your example, the switchToSecondary and switchToPrimary methods are
recreating the regions but not resetting the pointers to region1 and
region2. They are still pointing to the previous (closed) instances of the
Region.
Something like this should work:
this.region1 = clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
.setPoolName("B")
.create("region1");
Thanks,
Barry Oglesby
On Tue, May 5, 2020 at 11:14 AM aashish choudhary <
aashish.choudha...@gmail.com> wrote:
> ClientCache clientCache = new ClientCacheFactory().create();
> PoolFactory poolFactory = PoolManager.createFactory();
> poolFactory.addLocator("Locator11", 10334);
> poolFactory.addLocator("Locator22", 10334);
> poolFactory.create("A");
>
> poolFactory = PoolManager.createFactory();
> poolFactory.addLocator("Locator33", 10334);
> poolFactory.addLocator("Locator44", 10334);
> poolFactory.create("B");
>
> Region region11 =
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("A")
> .create("region1");
> Region region22 =
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("A")
> .create("region2");
>
>
> Region region33 =
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("B")
> .create("region1");
> Region region44 =
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("B")
> .create("region2");
> In normal scenario i don't switch pool and get Data from pool A only.To
> forcefully switch pools at runtime i have created and registered MBean.
> This MBean will have a flag for forcefully switching pools at runtime.
> For example if Mbean attribute secondaryPool is set to true then before
> fetching data it should call switchToSecondary. Likewise for the case of
> switching to primary pool.
> Sample code
> if(isPrimarypool){
> switchToPrimary();
> }
> if(isSecondarypool){
> switchToSecondary();
> }
>
> In the method switchToPrimary() this is what i am trying is something like
> below.
> switchToPrimary(){
> closeRegion();
> //then re-creating regions again something like this
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("A")
> .create("region1");
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("A")
> .create("region2");
> }
> In the method switchToSecondary() this is what i am trying is something
> like below
> switchToSecondary(){
> closeRegion();
> //then creating regions again
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("B")
> .create("region1");
> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
> .setPoolName("B")
> .create("region2");
> }
> closeRegion(){
> region1.close();
> region2.close();
> }
> Now the problem is if i switch to secondaryPool from primaryPool(changing
> Mbean attribute value) it works. But when i try to switch back to primary
> it says region destroyed.
> Let me know if you have any doubts about my approach. Basically i am
> trying to follow what is explained in the link i have shared earlier. As
> per that i have close and re create region if i need to switch. But i can't
> get handle to pool regions so that i can close regions pool wise It would
> have been easier that way but as you said that it's not possible for region
> to below to two pools.
>
> Also i have looked at your code not sure why you have to call
> keySetOnServer() method.
>
>
>
> With Best Regards,
> Ashish
>
>
> On Tue, May 5, 2020 at 11:03 PM Barry Oglesby <bogle...@pivotal.io> wrote:
>
>> Yes, you can't have a single region pointing at 2 pools. What I posted is
>> the way I've done it in the past. I just tried it, and it still works.
>> Maybe if you post your full code, I can take a look.
>>
>> Thanks,
>> Barry Oglesby
>>
>>
>>
>> On Tue, May 5, 2020 at 10:19 AM aashish choudhary <
>> aashish.choudha...@gmail.com> wrote:
>>
>>> Hi Barry,
>>>
>>> Thanks for the response.
>>>
>>> I am actually calling region.close() which I believe calls
>>> localDestroyRegion
>>> only. The problem is region names are same in both cluster so do how do I
>>> close region of cluster before switching to another cluster. I just want to
>>> switch pools based upon my use case at run-time.
>>>
>>> With best regards,
>>> Ashish
>>>
>>> On Tue, May 5, 2020, 10:25 PM Barry Oglesby <bogle...@pivotal.io> wrote:
>>>
>>>> Ashish,
>>>>
>>>> You're probably using region.destroyRegion to destroy the client
>>>> region. If so, that also destroys the region on the server.
>>>>
>>>> You should be able to use localDestroyRegion to just destroy the client
>>>> region like:
>>>>
>>>> // Get the region's key set using pool 1
>>>> Region pool11Region = createRegion(this.pool1.getName());
>>>> Set pool1Keys = pool1Region.keySetOnServer();
>>>> pool1Region.localDestroyRegion();
>>>>
>>>> // Get the region's key set using pool 2
>>>> Region pool2Region = createRegion(this.pool2.getName());
>>>> Set pool2Keys = pool2Region.keySetOnServer();
>>>> pool2Region.localDestroyRegion();
>>>>
>>>> The createRegion method is:
>>>>
>>>> private Region createRegion(String poolName) {
>>>> return this.cache
>>>> .createClientRegionFactory(ClientRegionShortcut.PROXY)
>>>> .setPoolName(poolName)
>>>> .create(this.regionName);
>>>> }
>>>>
>>>> Thanks,
>>>> Barry Oglesby
>>>>
>>>>
>>>>
>>>> On Tue, May 5, 2020 at 9:37 AM aashish choudhary <
>>>> aashish.choudha...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am sort of trying to implement a failover/failback for geode client.
>>>>> I have followed the approach the mentioned in here
>>>>> <https://community.pivotal.io/s/article/Configure-client-to-use-several-clusters>.
>>>>> I understand it's for gemfire but sharing just for reference as the use
>>>>> case is same and will apply this for geode as well. I hope that's ok.
>>>>>
>>>>> This is what i am trying to do. Creating two pools but in my case i
>>>>> have same region names in both cluster A and B.
>>>>> ClientCache clientCache = new ClientCacheFactory().create();
>>>>>
>>>>> PoolFactory poolFactory = PoolManager.createFactory();
>>>>> poolFactory.addLocator("Locator1", 10334);
>>>>> poolFactory.addLocator("Locator2", 10334);
>>>>> poolFactory.create("A");
>>>>>
>>>>> poolFactory = PoolManager.createFactory();
>>>>> poolFactory.addLocator("Locator1", 10334);
>>>>> poolFactory.addLocator("Locator2", 10334);
>>>>> poolFactory.create("B");
>>>>>
>>>>> Region region11 =
>>>>> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
>>>>> .setPoolName("A")
>>>>> .create("region1");
>>>>>
>>>>> Region region22 =
>>>>> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
>>>>> .setPoolName("A")
>>>>> .create("region2");
>>>>>
>>>>>
>>>>>
>>>>> Region region33 =
>>>>> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
>>>>> .setPoolName("B")
>>>>>
>>>>> .create("region1");
>>>>>
>>>>> Region region44 =
>>>>> clientCache.createClientRegionFactory(ClientRegionShortcut.PROXY)
>>>>> .setPoolName("B")
>>>>>
>>>>> .create("region2");
>>>>>
>>>>> So If a client needs to connect to regions with the same name in two
>>>>> different distributed systems then it must close or destroy the region
>>>>> and recreate it with the changed pool configuration each time it wants to
>>>>> change between two distributed systems.
>>>>>
>>>>> I am doing the same but getting region destroyed exception instead. I am
>>>>> using geode java client not spring data geode.
>>>>>
>>>>> How to do this? Please help.
>>>>>
>>>>>
>>>>>
>>>>> With Best Regards,
>>>>> Ashish
>>>>>
>>>>
