You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2023/05/18 08:32:00 UTC

[jira] [Commented] (IGNITE-19495) SQL onheap cache stores row on per-cache basis, but access these rows on per-index basis

    [ https://issues.apache.org/jira/browse/IGNITE-19495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723848#comment-17723848 ] 

Ignite TC Bot commented on IGNITE-19495:
----------------------------------------

{panel:title=Branch: [pull/10722/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10722/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7178894&amp;buildTypeId=IgniteTests24Java8_RunAll]

> SQL onheap cache stores row on per-cache basis, but access these rows on per-index basis
> ----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-19495
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19495
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: ise
>
> If there are two indexes on the same cache and sqlOnHeapCache property is enabled there can be node failures such as:
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is corrupted [groupId=-917681634, pageIds=[844420635164678], cacheId=-917681634, cacheName=..., indexName=_key_PK, msg=Runtime failure on row: Row@71aeb1b9[ ... ][  ]]
> ...
> Caused by: org.apache.ignite.IgniteException: Failed to store new index row.
> ...
> Caused by: java.lang.UnsupportedOperationException: 13 cannot be used for inline type 19
> {noformat}
> Root cause: {{IndexRowCache}} is created per cache group (see {{IndexRowCacheRegistry#onCacheRegistered}}), but stores {{IndexRowImpl}} binded to particular index (see {{InlineIndexTree#createIndexRow}}). In case, when another index requires the same data row, it gets row from the onheap cache with the wrong index row handler.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)