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

Roman Khachatryan commented on FLINK-36290:
-------------------------------------------

We hit this issue when cherry-picking changes from 1.19 branch to our internal 
fork.

It doesn't have FLINK-33750.

However, doing bisect and running through internal CI gave the following range 
of suspicious commits:
 - [docs] Update Java 17 compatibility docs
 - FLINK-36510[rpc] Bump Pekko to 1.1.2, remove Netty 3 
([de44f609ee687d87d55b269b4858ab9d7287b80b|https://github.com/apache/flink/commit/de44f609ee687d87d55b269b4858ab9d7287b80b]
 )
 - FLINK-36289[Connectors/Prometheus][docs] Integrate Prometheus connector docs 
into Flink website
 - FLINK-36668[docs] Update AWS docs for v5.0

>From which "FLINK-36510[rpc] Bump Pekko to 1.1.2, remove Netty 3" seems to be 
>the cause most likely.

> OutOfMemoryError in connect test run
> ------------------------------------
>
>                 Key: FLINK-36290
>                 URL: https://issues.apache.org/jira/browse/FLINK-36290
>             Project: Flink
>          Issue Type: Bug
>          Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile), Tests
>    Affects Versions: 2.0-preview
>            Reporter: Matthias Pohl
>            Priority: Blocker
>
> 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
> {code}
> 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
> [...]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to