You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dian Fu (Jira)" <ji...@apache.org> on 2020/05/18 03:08:00 UTC
[jira] [Closed] (FLINK-17700) The callback client of
JavaGatewayServer should run in a daemon thread
[ https://issues.apache.org/jira/browse/FLINK-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dian Fu closed FLINK-17700.
---------------------------
Resolution: Fixed
Merged to
- release-1.10 via 2bc4628876715698c9bae542e36014344a93c42b
- release-1.9 via 6ce59a8719d721f40aaf6551a91489a74683ddc5
> The callback client of JavaGatewayServer should run in a daemon thread
> ----------------------------------------------------------------------
>
> Key: FLINK-17700
> URL: https://issues.apache.org/jira/browse/FLINK-17700
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.9.0, 1.10.0
> Reporter: shuiqiangchen
> Assignee: shuiqiangchen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.2, 1.9.4
>
>
> When starting the JavaGatewayServer, a callback client would also be created and run in an ScheduleExecutorService's thread which is non-daemon by default. Thus, we need to shut down the non-daemon thread and reset a daemon thread back to the call back client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)