[IGNITE-11750] Implement locked pages info dump for long-running B+Tree operations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Assignee: Dmitriy Govorukhin
• Reporter: Alexey Goncharuk
• Created: 16/Apr/19 07:08
• Updated: 07/Jun/19 10:57
• Resolved: 05/Jun/19 10:01

Description

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.

Issue Links

• relates to: IGNITE-11899 Fix code style violation
• links to: GitHub Pull Request #6541
• links to: TC Run All