Actually to be more clear... http://xxxxxx-0001:8080/ignite?cmd=version responds immediately.
http://xxxxxx-0001:8080/ignite?cmd=size&cacheName=my-cache doesn't respond at all. On Tue, 5 Oct 2021 at 09:59, John Smith <java.dev....@gmail.com> wrote: > Yeah ever since I got this erro for example the REST APi wont return and > the request are slower. But when I connect with visor I can get stats I can > scan the cache etc... > > Is it possible that these async futures/threads are not released? > > On Tue, 5 Oct 2021 at 04:11, Zhenya Stanilovsky <arzamas...@mail.ru> > wrote: > >> Hi, this is just a warning shows that something suspicious observed. >> There is no simple reply for your question, in common case all these >> messages are due to cluster (resources or settings) limitation. >> Check documentation for tuning performance [1] >> >> [1] >> https://ignite.apache.org/docs/latest/perf-and-troubleshooting/general-perf-tips >> >> >> Hi, using 2.8.1 I understand the message as in my async TRX is taking >> longer but is there a way to prevent it? >> >> When this happened I was pushing about 50, 000 get/puts per second from >> my API. >> >> >> >> >> >> >
