I guess it could be caused by https://issues.apache.org/jira/browse/IGNITE-5003 which is mentioned in that thread. Also, make sure that your cache store code doesn’t cause you troubles – that you don’t open a new connection every time, don’t have unnecessary blocking, etc.
Stan From: Justin Ji Sent: 3 декабря 2018 г. 13:10 To: [email protected] Subject: RE: Ignite cache.getAll takes a long time Stan - Thank for your reply! Yes, the getAll and putAll(async) executed in parallel(amount of operations executed at the same time). But I think it may be caused by the write-behind, when I disabled the write-behind the timeout disappeared, and I enabled the write-behind the timeout appeared. It is a little similar to http://apache-ignite-users.70518.x6.nabble.com/write-behind-performance-impacting-main-thread-Write-behind-buffer-is-never-full-td17940.html -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
