Re: Failover in thin client mode

That's right. This IEP has been only implemented for C++ thin for now. Best Regards, Igor On Fri, Apr 26, 2019 at 2:05 PM kcheng.mvp wrote: > Hi Igor, > > I just checked the jiras and found this IPE has not been implemented for > *java thin client* yet ? > > > > >

Re: What's the difference between ClientCache#removeAll() and ClientCache#clear()

[image: image.png] There is no java doc about this. Anyway thank you very much! Thanks, Ken Cheng On Fri, Apr 26, 2019 at 7:52 PM Ilya Kasnacheev wrote: > Hello! > > Clear will not notify cache listeners or CacheWriters, but removeAll() > will. > > This is as per IgniteCache doc (which I

Re: Node joining didn't trigger Affinity recalculation problem

Hello! I guess this is because you can't join two clusters together. Once each node has formed a cluster at start, neither one can just other cluster. A cluster can accept nodes, new nodes can join to cluster, but two clusters can't merge. The only way here is to restart one of nodes. Regards,

Re: cache update slow

Hello! I think that comparing steady state benchmarks of multi-million operations versus 500 operations is misleading. 500 operations is probably not enough to gain full benefits from e.g. JIT. Regards, -- Ilya Kasnacheev пт, 26 апр. 2019 г. в 12:20, Coleman, JohnSteven (Agoda) <

Re: What happens when a client gets disconnected

Hello! Near cache's consistency is observed continuously, so I can see that there can be blocking if node greys out. Can you try and gather thread dumps from nodes during pause? Please collect as many nodes as possible. You can force cache lookups to go to near cache only if you use

Re: Apache Ignite support for continuous queries over sliding windows

Hello! Yes, you can do it via continuous query. Apache Ignite will send every entry to your continuous query but you will have to implement windowing yourself. I.e. remember the last N entries in a local data structure, discard entries that are no longer needed. Regards, -- Ilya Kasnacheev

Re: What's the difference between ClientCache#removeAll() and ClientCache#clear()

Hello! Clear will not notify cache listeners or CacheWriters, but removeAll() will. This is as per IgniteCache doc (which I guess is underlying here). Regards, -- Ilya Kasnacheev пт, 26 апр. 2019 г. в 05:10, kcheng.mvp : > Here is the code snippet from > org.apache.ignite.client.ClientCache

Re: Failover in thin client mode

Hi Igor, I just checked the jiras and found this IPE has not been implemented for *java thin client* yet ? https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20labels%20IN%20(iep-23)%20ORDER%20BY%20status%20%20%20%20%20%20%20 -- Sent from:

RE: cache update slow

Hi, Yes, comparing to DMA is apples and oranges comparison, but gives an idea of the relative gap in performance. A better comparison would be to an alike product such as NCache. They claims 20K wps*, thus 20 times faster than my ignite results, but obvs I'd have to compare using my scenario

RE: cache update slow

Glad you met your requirements. I think it is not fair to compare Ignite with direct memory access, so I can't really say whether this is a good result or not. In your case .net process starts a java process and communicates with it via JNI [1]. Also Ignite stores cache data off-heap, which

Re: Older client connections to Ignite blocking new clients

Hi, Could you provide logs from all the nodes, including servers and clients? Evgenii пт, 26 апр. 2019 г. в 11:04, mahesh76private : > Hi, > > We are experiencing a strange issue on ignite 2.7 for a few months now. > > we have 4 ignite clients (say GROUP1) connected to a ignite cluster >