ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Chugunov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11750) Implement locked pages info dump for long-running B+Tree operations
Date Fri, 31 May 2019 15:06:00 GMT

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

Sergey Chugunov commented on IGNITE-11750:
------------------------------------------

[~DmitriyGovorukhin],

Change looks good to me, please proceed with merging.

Thank you for contribution!

> Implement locked pages info dump for long-running B+Tree operations
> -------------------------------------------------------------------
>
>                 Key: IGNITE-11750
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11750
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I've stumbled upon an incident where a batch of Ignite threads were hanging on BPlusTree
operations trying to acquire read or write lock on pages. From the thread dump it is impossible
to check if there is an issue with {{OffheapReadWriteLock}} or there is a subtle deadlock
in the tree.
> I suggest we implement a timeout for page lock acquire and tracking of locked pages.
This should be relatively easy to implement in {{PageHandler}} (the only thing to consider
is performance degradation). If a timeout occurs, we should print all the locks currently
owned by a thread. This way we should be able to determine if there is a deadlock in the {{BPlusTree}}.



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

Mime
View raw message