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

OutOfMemoryError in connect test run

    XMLWordPrintableJSON

Details

    Description

      We saw a OOM in the connect stage that's caused a fatal error:
      https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=62173&view=logs&j=1c002d28-a73d-5309-26ee-10036d8476b4&t=d1c117a6-8f13-5466-55f0-d48dbb767fcd&l=12182

      03:19:59,975 [   flink-scheduler-1] ERROR org.apache.flink.util.FatalExitExceptionHandler              [] - FATAL: Thread 'flink-scheduler-1' produced an uncaught exception. Stopping the process...
java.lang.OutOfMemoryError: Java heap space
[...]
03:19:59,981 [jobmanager_62-main-scheduler-thread-1] ERROR org.apache.flink.util.FatalExitExceptionHandler              [] - FATAL: Thread 'jobmanager_62-main-scheduler-thread-1' produced an uncaught exception. Stopping the process...
java.lang.OutOfMemoryError: Java heap space
[...]

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. FLINK-36291 java.lang.IllegalMonitorStateException causing a fatal error on the TaskManager side

          • Blocker - Blocks development and/or testing work, production could not run
          • Open

          Activity

            People

              Unassigned Unassigned
              mapohl Matthias Pohl
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: