You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/10/17 14:49:00 UTC
[jira] [Closed] (FLINK-10582) Make REST executor thread priority
configurable
[ https://issues.apache.org/jira/browse/FLINK-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-10582.
------------------------------------
Resolution: Fixed
master: 3f231ac46537654aebdd73b0f42aa823386bf901
1.6: 967b31b333e6f4b014ea3041f420bfaff2484618
1.5: 98f38288a12065dd665f7e0b2420d57f6408121a
> 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, 1.5.5, 1.6.2
>
>
> 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)