[
https://issues.apache.org/jira/browse/FLINK-37317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jufang He updated FLINK-37317:
------------------------------
Description:
org.apache.flink.streaming.runtime.tasks.StreamTask#AsyncOperationsThreadPool
configuration looks unreasonable, cause in fact will only have one thread to
run. The concurrent checkpoints asyncCheckpointRunnable execution and close can
only run serially. The thread pool configuration is as follows:
!image-2025-02-13-17-23-11-788.png!
I simulated the execution of the thread pool locally, and the results were as
follows:
!image-2025-02-13-17-25-47-904.png!
!image-2025-02-13-17-26-04-449.png!
I think there are the following ways to solve this problem:
1、Increases the corePoolSize, but increases CPU consumption.
2、Use CachedThreadPool which uses SynchronousQueue as the workQueue, and the
tasks execute immediately. But too many tasks can take up too many resources.
was:
org.apache.flink.streaming.runtime.tasks.StreamTask#AsyncOperationsThreadPool
configuration looks unreasonable, cause in fact will only have one thread to
run. The concurrent checkpoints asyncCheckpointRunnable execution and close can
only run serially. The thread pool configuration is as follows:
!image-2025-02-13-17-25-01-252.png!
I simulated the execution of the thread pool locally, and the results were as
follows:
!image-2025-02-13-17-25-47-904.png!
!image-2025-02-13-17-26-04-449.png!
I think there are the following ways to solve this problem:
1、Increases the corePoolSize, but increases CPU consumption.
2、Use CachedThreadPool which uses SynchronousQueue as the workQueue, and the
tasks execute immediately. But too many tasks can take up too many resources.
> Checkpoint asyncOperationsThreadPool has only one thread running
> ----------------------------------------------------------------
>
> Key: FLINK-37317
> URL: https://issues.apache.org/jira/browse/FLINK-37317
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.20.1
> Reporter: Jufang He
> Priority: Major
> Attachments: image-2025-02-13-17-23-11-788.png,
> image-2025-02-13-17-25-47-904.png, image-2025-02-13-17-26-04-449.png
>
>
> org.apache.flink.streaming.runtime.tasks.StreamTask#AsyncOperationsThreadPool
> configuration looks unreasonable, cause in fact will only have one thread to
> run. The concurrent checkpoints asyncCheckpointRunnable execution and close
> can only run serially. The thread pool configuration is as follows:
> !image-2025-02-13-17-23-11-788.png!
> I simulated the execution of the thread pool locally, and the results were as
> follows:
> !image-2025-02-13-17-25-47-904.png!
> !image-2025-02-13-17-26-04-449.png!
> I think there are the following ways to solve this problem:
> 1、Increases the corePoolSize, but increases CPU consumption.
> 2、Use CachedThreadPool which uses SynchronousQueue as the workQueue, and the
> tasks execute immediately. But too many tasks can take up too many resources.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
