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 2019/04/26 10:24:00 UTC

[jira] [Closed] (FLINK-12317) BlockingCallMonitoringThreadPool fails on Java 9

     [ https://issues.apache.org/jira/browse/FLINK-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-12317.
------------------------------------
    Resolution: Fixed

master: 7347c9e2094c5243ef7db34bde1fd87ea5e7641d

> BlockingCallMonitoringThreadPool fails on Java 9
> ------------------------------------------------
>
>                 Key: FLINK-12317
>                 URL: https://issues.apache.org/jira/browse/FLINK-12317
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Checkpointing, Tests
>    Affects Versions: 1.9.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The {{BlockingCallMonitoringThreadPool}} modifies the core/maximum pool size of an underlying executor. It always first modifies the core size, and then the maximum size. When increasing the pool size it thus follows that core size at one point exceeds the maximum. This is fine on java 8, but no longer allowed on Java 9.



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