Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.1.3
    • None
    • Runtime / Coordination
    • None

    Description

      A JobManager that ever encountered an OutOfMemoryError is with a high probability not functional any more. However, the OutOfMemoryError kills only the thread where it is thrown by default, not the entire JVM.

      We should add -XX:OnOutOfMemoryError="kill -9 %p" both to the standalone bash options and to the YARN and Mesos launch options.

      On the TaskManager side, the decision is more tricky and less critical, so I suggest to add this only to the JobManager by default.

      Attachments

        Activity

          yanghua vinoyang added a comment - - edited

          Hi sewen the JDK8, (more precisely since JDK 8u92, pelase see : http://www.oracle.com/technetwork/java/javase/8u92-relnotes-2949471.html), there are two new JVM options:

          • ExitOnOutOfMemoryError - When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors.
          • CrashOnOutOfMemoryError - If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files (if core files are enabled).

           I think for old JDK we can use 'OnOutOfMemoryError' option, however, higher JDK these options would be better to fix the OOMError.

          What's your opinion?

          yanghua vinoyang added a comment - - edited Hi sewen  the JDK8, (more precisely since JDK 8u92, pelase see : http://www.oracle.com/technetwork/java/javase/8u92-relnotes-2949471.html ), there are two new JVM options: ExitOnOutOfMemoryError  - When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors. CrashOnOutOfMemoryError  - If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files (if core files are enabled).  I think for old JDK we can use 'OnOutOfMemoryError' option, however, higher JDK these options would be better to fix the OOMError. What's your opinion?
          yanghua vinoyang added a comment - - edited

          sewen Hope for listening to your comments.

          yanghua vinoyang added a comment - - edited sewen Hope for listening to your comments.
          flink-jira-bot Flink Jira Bot added a comment -

          This major issue is unassigned and itself and all of its Sub-Tasks have not been updated for 30 days. So, it has been labeled "stale-major". If this ticket is indeed "major", please either assign yourself or give an update. Afterwards, please remove the label. In 7 days the issue will be deprioritized.

          flink-jira-bot Flink Jira Bot added a comment - This major issue is unassigned and itself and all of its Sub-Tasks have not been updated for 30 days. So, it has been labeled "stale-major". If this ticket is indeed "major", please either assign yourself or give an update. Afterwards, please remove the label. In 7 days the issue will be deprioritized.

          Removed "stale-critical|major|minor" label in line with https://issues.apache.org/jira/browse/FLINK-22429.

          knaufk Konstantin Knauf added a comment - Removed "stale-critical|major|minor" label in line with https://issues.apache.org/jira/browse/FLINK-22429 .

          People

            Unassigned Unassigned
            sewen Stephan Ewen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: