You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (Jira)" <ji...@apache.org> on 2020/04/16 16:08:00 UTC
[jira] [Assigned] (IGNITE-8409) Ignite gets stuck on
IgniteDataStreamer.addData when using Object with AffinityKeyMapped
[ https://issues.apache.org/jira/browse/IGNITE-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk reassigned IGNITE-8409:
----------------------------------------
Assignee: (was: Alexey Goncharuk)
> Ignite gets stuck on IgniteDataStreamer.addData when using Object with AffinityKeyMapped
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-8409
> URL: https://issues.apache.org/jira/browse/IGNITE-8409
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Andrey Aleksandrov
> Priority: Critical
> Fix For: 2.9, 2.8.1
>
> Attachments: ContextCpty.java, TradeKey.java, TradeKeyNew.java
>
>
> This problem reproduces from time to time when we are streaming the data (TradeKey.java) to Ignite sql cache. As AffinityKeyMapped we used the object type (ContextCpty.java)
> When we change AffinityKeyMapped type from object to long type (TradeKeyNew.java) then problem disappears.
> Investigation help to understand that we hang in BPlusTree.java class in next method:
> private Result putDown(final Put p, final long pageId, final long fwdId, final int lvl)
> In this method:
> res = p.tryReplaceInner(pageId, page, fwdId, lvl);
> if (res != RETRY) // Go down recursively.
> res = putDown(p, p.pageId, p.fwdId, lvl - 1);
> if (res == RETRY_ROOT || p.isFinished())
> return res;
> if (res == RETRY)
> checkInterrupted(); //WE ALWAYS GO TO THIS PLACE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)