quot; +
>>> cctx.name() +
>>> ", locStart=" + cctx.startTopologyVersion() +
>>> ", locNode=" + cctx.localNode() +
>>> ", stopping=" + cctx.kernalContext().isStopping();
>>>
>>> Cach
>
>
>
> regards,
> Veena.
>
> On Tue, Dec 14, 2021 at 2:11 PM Veena Mithare
> wrote:
>
>>
>>
>> Hi Team,
>>
>>
>>
>> Just following up on this .
>>
>>
>>
>> My question is ,
>>
>>
>>
>>
My question is ,
>>
>>
>>
>> If : There is an update on a cache and there are a few clients listening to
>> the cache update changes - >
>> should notification failure to a few clients( because of network issues etc.
>> experienced by the Com
ssues etc.
> experienced by the Communication SPI ), delay notification to the other
> clients interested.
>
>
> If point b is true, wouldn’t that be a bug ..
>
>
>
> Regards,
>
> Veena.
>
>
>
> From: Veena Mithare
> Sent: 10 December 2
SPI ), delay notification to the other
clients interested.
If point b is true, wouldn't that be a bug ..
Regards,
Veena.
From: Veena Mithare
Sent: 10 December 2021 17:22
To: 'user@ignite.apache.org'
Subject: RE: Delay in receiving notifications 2.8.1
The delay seems to match the conne
],
failureDetectionTimeoutEnabled=false, timeout=2510, err=null,
addr=/fde1:53ba:e9a0:de11:f602:70ff:fef0:ecab%idrac:47100]
the configuration give is as below :
From: Veena Mithare
Sent: 10 December 2021 17:16
To: user@ignite.apache.org
Subject: Delay in receiving notifications 2.8.1
Hi Team,
We
Hi Team,
We have a 3 node cluster on 2.8.1 . And we have around 30 clients and around
20 of them have continuous query registered against the same cache ( say CACHEA
)
We faced the below scenario :
1. Cache A was updated .
2. A few clients( say 4 or 5 ) received the update with 1 or 2
