Spread bets and CFDs are complex instruments and come with a high risk of
losing money rapidly due to leverage. 66% of retail investor accounts lose
money when spread betting and/or trading CFDs with this provider. You should
consider whether you understand ho
Spread bets and CFDs are complex instruments and come with a high risk of
losing money rapidly due to leverage. 66% of retail investor accounts lose
money when spread betting and/or trading CFDs with this provider. You should
consider whether you understand ho
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
],
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
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
Hello all,
We observed a weird state in our cluster last week. We are on 2.8.1 cluster
We have about 20 clients connected to a 3 node server cluster . Discovery
spi issues
=
1. Server and client nodes were restarted one after the oth
alContext().isStopping();
CacheContinuousQueryEvent evt = new CacheContinuousQueryEvent<>(jcache,
cctx, e0);
lsnr.onEntryUpdated(evt, primary, recordIgniteEvt, fut);
}
}
regards,
Veena.
On Tue, Dec 14, 2021 at 2:11 PM Veena Mithare wrote:
>
>
> Hi Team
Hello,
Not sure if you are still facing this issue,
When we would face this issue , we would find which client node is the
baseline command saying is not found. And restart that client node.
Sometimes after restarting the client node, the baseline command would say
the same thing about another c
Hi,
Any idea if this is fixed any later version of ignite?
If not I will raise a bug .
Regards
Veena
Sent from my iPhone
> On 20 Jun 2022, at 09:19, Veena Mithare wrote:
>
>
>
> Hi ,
>
> This issue was observed again in our environment. We have a cluster of 20
>
rnalContext().cache().jcacheProxy(*cctx*.name(), *true*);
>
> *assert *jcache != *null *: *"Failed to get cache proxy [name=" *+
> *cctx*.name() +
> *", locStart=" *+ *cctx*.startTopologyVersion() +
> *", locNode=" *+ *cctx*.loca
Just to mention we do have @IgniteAsyncCallback annotation on our remote filter
and local listener.We use Continuous query with transformer. Will raise a bug
Sent from my iPhone
> On 23 Jun 2022, at 08:35, Veena Mithare wrote:
>
>
> Hi ,
>
> Can someone kindly help me
11 matches
Mail list logo
