[
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 auto-deprioritized-minor (was: Monitoring
Netty REST stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: Monitoring, Netty, REST, auto-deprioritized-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)
