Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-18153

flink-daemon does not detect errors if JVM crashes immediately

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 1.11.0
    • None
    • Runtime / Coordination
    • None

    Description

      Configuring obscenely large amounts of memory that exceed the machine, which prevents the JVM startup, does not result in any error to be printed to the console. The logs are empty, and the only hint for an error is found in the .out file.

      OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007aaf70000000, 5241403604992, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 5241403604992 bytes for committing reserved memory.

      This behavior is just a bit too subtle.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue FLINK-17973 Test memory configuration of Flink cluster

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. FLINK-13980 FLIP-49 Unified Memory Configuration for TaskExecutors

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. FLINK-16614 FLIP-116 Unified Memory Configuration for Job Manager

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              chesnay Chesnay Schepler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: