[ 
https://issues.apache.org/jira/browse/FLINK-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653650#comment-16653650
 ] 

ASF GitHub Bot commented on FLINK-10582:
----------------------------------------

zentol commented on a change in pull request #6868: [FLINK-10582] Make REST 
executor's thread priority configurable
URL: https://github.com/apache/flink/pull/6868#discussion_r225961269
 
 

 ##########
 File path: 
flink-core/src/main/java/org/apache/flink/configuration/RestOptions.java
 ##########
 @@ -121,4 +122,12 @@
                key("rest.server.numThreads")
 
 Review comment:
   i guess I didn't follow naming conventions here? we could still hotfix that.

----------------------------------------------------------------
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


> Make REST executor thread priority configurable
> -----------------------------------------------
>
>                 Key: FLINK-10582
>                 URL: https://issues.apache.org/jira/browse/FLINK-10582
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime, REST
>    Affects Versions: 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> With FLINK-10282, we introduced a dedicated thread pool for the REST server 
> endpoint. The thread priority was set to {{Thread.MIN_PRIORITY}}. This, 
> however, might affect existing users by making some of the REST calls no 
> longer responsive (e.g. if the other components' threads take all the time). 
> Therefore, I propose to set the default thread priority to 
> {{Thread.NORM_PRIORITY}} and make it additionally configurable such that 
> users can change it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to