You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Aleksandrov (JIRA)" <ji...@apache.org> on 2018/04/27 10:34:00 UTC
[jira] [Created] (IGNITE-8409) Ignite gets stuck on
IgniteDataStreamer.addData when using Object with AffinityKeyMapped
Andrey Aleksandrov created IGNITE-8409:
------------------------------------------
Summary: 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
Fix For: 2.6
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
(v7.6.3#76005)