Val,
Are the interceptors invoked in the affinity co-located context of the item?
The help is a little unclear on that.
Thanks,
Raymond.
Sent from my iPhone
> On 28/04/2018, at 12:12 PM, vkulichenko wrote:
>
> Raymond,
>
> If you go with approach I described
Raymond,
If you go with approach I described above, I would actually recommend to use
interceptors:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheInterceptor.html
Continuous query seems to be a bit cumbersome for this.
-Val
--
Sent from:
If I use local continuous queries can't I omit the remote filter and just use
the local delivery handler for the continuous query?
Sent from my iPhone
> On 28/04/2018, at 9:43 AM, vkulichenko wrote:
>
> Raymond,
>
> It sounds like you want to run certain
Raymond,
It sounds like you want to run certain computation on every data update in
the cache, is that right?
To achieve that you can use local continuous queries, but:
- Remote filter would be executed on both primary and backup, so computation
will be executed more than once.
- You can filter
Nick,
Here are some comments on your questions:
1. Heartbeat is always sent to the next node in the ring. That's the whole
point of the ring architecture vs. peer-to-peer.
2. That's not possible, because each discovery message is sent across the
ring, and the ordering of those messages is
Hi,
Try to disable IPv6 on all nodes via JVM option -Djava.net.preferIPv4Stack=true
[1]
as using both IPv4 and IPv6 can cause grid segmentation.
[1]
https://stackoverflow.com/questions/11850655/how-can-i-disable-ipv6-stack-use-for-ipv4-ips-on-jre
On Fri, Apr 27, 2018 at 8:52 AM, naresh.goty