[
https://issues.apache.org/jira/browse/FLINK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623298#comment-16623298
]
ASF GitHub Bot commented on FLINK-10282:
----------------------------------------
TisonKun commented on issue #6661: FLINK-10282][runtime] Separate RPC and REST
thread-pools
URL: https://github.com/apache/flink/pull/6661#issuecomment-423466269
Once introduce a new thread-pool to deal with REST tasks, we need to manage
its lifecycle inside `WebMonitorEndpoint` instead of initial it at
`ClusterEntrypoint`.
To make it more clear, we should pass a argument that how much threads the
thread-pool should contain instead of a `Executor`, and init `ExecutorService`
in `WebMonitorEndpoint`. Also, when shutdown the endpoint, shutdown the service.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Provide separate thread-pool for REST endpoint
> ----------------------------------------------
>
> Key: FLINK-10282
> URL: https://issues.apache.org/jira/browse/FLINK-10282
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime, REST
> Affects Versions: 1.5.1, 1.6.0, 1.7.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> The REST endpoints currently share their thread-pools with the RPC system,
> which can cause the Dispatcher to become unresponsive if the REST parts are
> overloaded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
