You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/10/16 22:35:00 UTC
[jira] [Comment Edited] (FLINK-10247) Run MetricQueryService in
separate thread pool
[ https://issues.apache.org/jira/browse/FLINK-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646054#comment-16646054 ]
Till Rohrmann edited comment on FLINK-10247 at 10/16/18 10:34 PM:
------------------------------------------------------------------
Fixed via
1.7.0:
13256d17d032dae1f603a4047d688cf45a44068e
3ad66f2463ee9ae4d61bb45146cf2dd5cb89cdcb
ad530862747090438880857a2e917f528b6d75e0
d7550d6a6e384546b25ca1e4d76dd26ca539973a
cbed19c45f83e739c316fd011ce5334ed44712f2
was (Author: till.rohrmann):
Fixed via
1.7.0:
13256d17d032dae1f603a4047d688cf45a44068e
3ad66f2463ee9ae4d61bb45146cf2dd5cb89cdcb
ad530862747090438880857a2e917f528b6d75e0
d7550d6a6e384546b25ca1e4d76dd26ca539973a
cbed19c45f83e739c316fd011ce5334ed44712f2
1.6.2:
9f593cd23d130b5a1266bd68ea5b34860c170c39
bb3eba40d68011be5e58136695f03df45a3b6d79
03ab3a3f4f368f266d25e8130f0a8d1a3ae33c09
1496c44fe8f241195a513616a4bfa8091bdcff3b
1cdababc2826681bf2ecfb1b7261dad4bff4b2b9
1.5.5:
1368d1be56dc4c73506580eda3d38f0a965edd3c
6974916f1554d263c48493aab93bd09db4f87ca2
b24c3c3632f78e47de95a4784cabec4344e480d2
4b5c447530816cbf47fcd103bc42795c00584357
df796122e6a71d9aeadcfbf3b5f628e0e036bb0b
> Run MetricQueryService in separate thread pool
> ----------------------------------------------
>
> Key: FLINK-10247
> URL: https://issues.apache.org/jira/browse/FLINK-10247
> Project: Flink
> Issue Type: Sub-task
> Components: Metrics
> Affects Versions: 1.5.3, 1.6.0, 1.7.0
> Reporter: Till Rohrmann
> Assignee: Shimin Yang
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> In order to make the {{MetricQueryService}} run independently of the main Flink components, it should get its own dedicated thread pool assigned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)