You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2026/07/31 22:41:00 UTC

[jira] [Reopened] (FLINK-39900) Support configuring the number of threads used in ForStStateDataTransfer

     [ https://issues.apache.org/jira/browse/FLINK-39900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Nuyanzin reopened FLINK-39900:
-------------------------------------

> Support configuring the number of threads used in ForStStateDataTransfer
> ------------------------------------------------------------------------
>
>                 Key: FLINK-39900
>                 URL: https://issues.apache.org/jira/browse/FLINK-39900
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>            Reporter: Francis
>            Assignee: Francis
>            Priority: Not a Priority
>              Labels: pull-request-available
>             Fix For: 2.4.0
>
>
> Currently it is not possible to configure the thread pool used in the 
> `ForStStateDataTransfer` class. This limits the amount of threads available when transferring or writing state using ForSt. Whenever a `ForStStateDataTransfer` class is created, the default `DEFAULT_THREAD_NUM` of 4 is passed in via the class constructor. 
>  
> When working with Flink applications that handle large amounts of state it would be helpful to tune this value. We should add a `ConfigOption` that allows configuring the amount of threads made available to the `ForStStateDataTransfer` class.



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