[IGNITE-11265] Node stop causes JVM Crashes in page memory

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.7.5
• Assignee: Eduard Shangareev
• Reporter: Dmitry Pavlov
• Created: 08/Feb/19 12:28
• Updated: 11/Jun/19 15:47
• Resolved: 14/Feb/19 17:55

Description

Reproduced on Teamcity:All crash dumps complain about the same method
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock

Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882)
https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log

Other recent examples
Queries 1
https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log

Client Nodes
https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log

Zookeeper Discovery
https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log

Issue Links

• blocks: IGNITE-11189 Support Java 11 for Apache Ignite
• is duplicated by: IGNITE-11264 JVM crash in OffheapReadWriteLock#tryWriteLock
• links to: GitHub Pull Request #6092