Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-11769

Investigate JVM crash in PDS Direct IO TeamCity suites

    XMLWordPrintableJSON

    Details

      Description

      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

      # [ timer expired, abort... ]
      Process finished with exit code 134 (interrupted by signal 6: SIGABRT
      

      and the following error messages can be dumped to stderr before process death

      corrupted double-linked list
      free(): corrupted unsorted chunks
      

      which appear to be libc error messages. Seems like Ignite corrupts virtual memory in sophisticated way which prevents normal JVM crash flow.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ivan.glukos Ivan Rakov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: