ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7698) Page read during replacement should be outside of segment write lock
Date Thu, 22 Feb 2018 17:54:00 GMT

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

ASF GitHub Bot commented on IGNITE-7698:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/3560


> Page read during replacement should be outside of segment write lock
> --------------------------------------------------------------------
>
>                 Key: IGNITE-7698
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7698
>             Project: Ignite
>          Issue Type: Improvement
>          Components: persistence
>    Affects Versions: 2.1
>            Reporter: Alexey Goncharuk
>            Assignee: Dmitriy Pavlov
>            Priority: Major
>             Fix For: 2.5
>
>
> When a page is acquired, if it needs to be read from disk, we read it inside the segment
write lock which blocks other threads from acquiring pages that are already in memory.
> This can be easily avoided: once we initialized the page's being loaded RW lock, we can
immediately acquire the write lock - no deadlocks can happen here. Afterwards, we can release
the segment write lock and read the page.
> The change seems to be very local.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message