gion indicates a region named AuthIdRegion
>> with a subregion also named AuthIdRegion.
>>
>> -Dan
>>
>> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar
>> wrote:
>>
>>> we are using apache geode 1.1.0 version. sometimes randomly while trying
>&g
hIdRegion indicates a region named AuthIdRegion
>> with a subregion also named AuthIdRegion.
>>
>> -Dan
>>
>> On Mon, Dec 2, 2019 at 8:04 PM Rajesh Kumar
>> wrote:
>>
>>> we are using apache geode 1.1.0 version. sometimes randomly while trying
always the same: the client application was trying to execute the
> operation on a server that didn't have the region created. As Dan pointed
> out, I'd suggest to double check whether you have the region
> *AuthIdRegion* configured in all your servers.
> Best regards.
>
>
> On Wed,
implify the way you code
> and interact with the Geode system.
>
> --Udo
> On 12/2/19 8:04 PM, Rajesh Kumar wrote:
>
> we are using apache geode 1.1.0 version. sometimes randomly while trying
> to get details from a region we are getting exceptions. On looking at the
leading, though, it shouldn't contain the name twice and it
> would probably be better to throw something like *RegionNotFoundException*
> instead
> of *RegionDestroyedException*, but that's another discussion.
>
> Cheers.
>
> On Wed, Dec 4, 2019 at 10:32 AM Rajesh Kumar
> wrote:
&
Hi All.
we are using Geode 1.8.0 in peer to peer configuration.
I am facing a problem where a locator is not able to join the
distributed system.
>From the logs I can see that the locator is attempting to join through the
coordinator but it is not able to join. It keeps retrying with the
