[jira] [Commented] (IGNITE-11769) Investigate JVM crash in PDS Direct IO TeamCity suites

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

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

Maxim Muzafarov commented on IGNITE-11769:
------------------------------------------

Moved to 2.9 due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.

> Investigate JVM crash in PDS Direct IO TeamCity suites
> ------------------------------------------------------
>
>                 Key: IGNITE-11769
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11769
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Ivan Rakov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> Both PDS Direct IO suites periodically fail with JVM crash.
> The issue can be reproduced on Linux machine by running IgnitePdsWithTtlTest#testTtlIsAppliedAfterRestart using ignite-direct-io classpath.
> The investigation is complicated because JVM crash report *is not generated* during crash. After some point, JVM stays dormant for 2 minutes (waiting for JVM crash handling activities timeout) and then the process gets killed
> {code:java}
> # [ timer expired, abort... ]
> Process finished with exit code 134 (interrupted by signal 6: SIGABRT
> {code}
> and the following error messages can be dumped to stderr before process death
> {code:java}
> corrupted double-linked list
> free(): corrupted unsorted chunks
> {code}
> which appear to be libc error messages. Seems like Ignite corrupts virtual memory in sophisticated way which prevents normal JVM crash flow.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)