RE: Query execution too long even after providing index

Guys, is there any solution for this? Can someone please respond? Thanks, Prasad -- Forwarded message - From: Prasad Bhalerao Date: Fri, Sep 7, 2018, 8:04 AM Subject: Fwd: Query execution too long even after providing index To: Can we have update on this? -- Forwarde

Re: The system cache size was slowly increased

Prem - Thank for your reply. You explained why Ignite container grew from 2.5G to more than 4G because there is 2G heap memory and more than 2G off-heap memory, I think what you said is very correct and solve one of my main problems. But another question, why system memory cache also grows s

Re: Connection reset by peer

Thank you Ilya, I found that I increased this timeout on server side but not on client side, i guess this should be the problem, it should be the client who closed the connection. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Eviction Policy on Dirty data

With writeThrough an entry in the cache will never be "dirty" in that sense - cache store will update the backing DB at the same time the cache update happens. From: monstereo Sent: 14 августа 2018 г. 22:39 To: user@ignite.apache.org Subject: Re: Eviction Policy on Dirty data yes, using cachest

Re: How to throttle/limit the cache-store read threads?

Hi Mridul, Have you considered the option of creating a dedicated Threadpool for the cache store operations. Here is an example http://commons.apache.org/dormant/threadpool/ Another option would be to consider Hystrix Command Threadpool since you mentioned that the cache store is remote web serv