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

[jira] [Commented] (IGNITE-18736) Prepare class AbstractPageMemoryMvPartitionStorage cursors for working with locks

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

Roman Puchkovskiy commented on IGNITE-18736:
--------------------------------------------

The patch looks good to me, thanks!

> Prepare class AbstractPageMemoryMvPartitionStorage cursors for working with locks
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-18736
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18736
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> We need to prepare cursors for working with locks, which should solve the problems of parallel modifications and reading version chains.
> *org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage#scanVersions* - we need to read the entire chain at once. Since after reading one of the elements of the chain, any modification of the links to the next element can occur, we can degrade to quadratic complexity.
> *org.apache.ignite.internal.storage.pagememory.mv.AbstractPageMemoryMvPartitionStorage#scan* - we will need to try to immediately find the version by *timestamp* when reading the chain, since the *BplusTree* cursor caches rows that are on the same page.



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