You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/06 10:41:00 UTC

[jira] [Updated] (FLINK-23321) Make JM REST Netty thread pool count configurable

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

Flink Jira Bot updated FLINK-23321:
-----------------------------------
    Labels: Monitoring Netty REST stale-minor  (was: Monitoring Netty REST)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Make JM REST Netty thread pool count configurable
> -------------------------------------------------
>
>                 Key: FLINK-23321
>                 URL: https://issues.apache.org/jira/browse/FLINK-23321
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics, Runtime / REST
>            Reporter: Nicolas Raga
>            Priority: Minor
>              Labels: Monitoring, Netty, REST, stale-minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Currently [rest.server.numThreads|https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/deployment/config/#rest-server-numthreads] works to create more DispatcherRestEndpoint threads which help in high usage of functionality in the purview of job the dispatcher functionality. However, we cannot tune the number of netty threads use to handle requests. Especially when using the REST server as a monitoring endpoint, a lack of netty threads when processing of AbstractHandlers takes a long causes extended response times. 
> Such configuration already exists for taskmanagers (*taskmanager.network.netty.client/server.numThreads*) and such implementation of a *server.netty-boss.numThreads* and *server.netty-worker.numThreads* would be of great use.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)