You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Alper Tekinalp <al...@evam.com> on 2018/10/25 06:32:53 UTC
Cache access blocked on destroy
Hi all.
We have such a use case that we regularly create and destroy caches on run
time. But when we destroy a cache accesses to other caches could be blocked
and our worker threads not processing any data.
Is it an expected behaviour? Is there a better way or workaround? Any
suggestions or comments?
Regards.
--
Alper Tekinalp
Software Development Team Lead
Evam Streaming Analytics
www.evam.com <http://www.evam.com.tr>
<http://www.evam.com>
Re: Cache access blocked on destroy
Posted by "ilya.kasnacheev" <il...@gmail.com>.
Hello!
Unfortunately your e-mail contained neither attachment nor links to it.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Cache access blocked on destroy
Posted by Alper Tekinalp <al...@evam.com>.
Hi.
You can find stacktrace from 2 nodes while destroying cache. Our primary
worker threads are AsyncWorker-*. For about 40 seconds between 24/Oct/2018
15:52:51 - 24/Oct/2018 15:53:28 threads waiting for cache to be destroyed.
As a note I can say that is not an issue every time.
On Thu, Oct 25, 2018 at 6:09 PM akurbanov <an...@gmail.com> wrote:
> Hello,
>
> I would definitely suggest you to upgrade to latest Ignite versions as a
> vast number of issues has been fixed since 1.9:
> https://issues.apache.org/jira/browse/IGNITE-6035
> https://issues.apache.org/jira/browse/IGNITE-2714
> https://issues.apache.org/jira/browse/IGNITE-8531
> https://issues.apache.org/jira/browse/IGNITE-8021
> https://issues.apache.org/jira/browse/IGNITE-7319
>
> Please pay attention to the last one, this seems to be exactly your use
> case. A lot of things happen on both node and cluster levels when you call
> cache.destroy(), since this is a minor exchange which involves all server
> nodes where this cache exists, also a checkpoint along with write-ahead log
> flush is performed.
>
> Anyway, could you please give more details on how exactly your issue is
> meant to be reproduced (check the code on IGNITE-7319 if it is looks like
> your case), provide some logs and thread dumps to analyze.
>
> Regards,
> Anton
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Alper Tekinalp
Software Development Team Lead
Evam Streaming Analytics
www.evam.com <http://www.evam.com.tr>
<http://www.evam.com>
Re: Cache access blocked on destroy
Posted by akurbanov <an...@gmail.com>.
Hello,
I would definitely suggest you to upgrade to latest Ignite versions as a
vast number of issues has been fixed since 1.9:
https://issues.apache.org/jira/browse/IGNITE-6035
https://issues.apache.org/jira/browse/IGNITE-2714
https://issues.apache.org/jira/browse/IGNITE-8531
https://issues.apache.org/jira/browse/IGNITE-8021
https://issues.apache.org/jira/browse/IGNITE-7319
Please pay attention to the last one, this seems to be exactly your use
case. A lot of things happen on both node and cluster levels when you call
cache.destroy(), since this is a minor exchange which involves all server
nodes where this cache exists, also a checkpoint along with write-ahead log
flush is performed.
Anyway, could you please give more details on how exactly your issue is
meant to be reproduced (check the code on IGNITE-7319 if it is looks like
your case), provide some logs and thread dumps to analyze.
Regards,
Anton
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Cache access blocked on destroy
Posted by Alper Tekinalp <al...@evam.com>.
My ignite version is 1.9
On Thu, Oct 25, 2018 at 9:32 AM Alper Tekinalp <al...@evam.com> wrote:
> Hi all.
>
> We have such a use case that we regularly create and destroy caches on run
> time. But when we destroy a cache accesses to other caches could be blocked
> and our worker threads not processing any data.
>
> Is it an expected behaviour? Is there a better way or workaround? Any
> suggestions or comments?
>
> Regards.
>
> --
> Alper Tekinalp
>
> Software Development Team Lead
> Evam Streaming Analytics
>
> www.evam.com <http://www.evam.com.tr>
> <http://www.evam.com>
>
--
Alper Tekinalp
Software Development Team Lead
Evam Streaming Analytics
www.evam.com <http://www.evam.com.tr>
<http://www.evam.com>