flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (Jira)" <j...@apache.org>
Subject [jira] [Created] (FLINK-15791) Don't use ForkJoinPool#commonPool() for executing asynchronous operations in Fabric8FlinkKubeClient
Date Tue, 28 Jan 2020 16:03:00 GMT
Till Rohrmann created FLINK-15791:
-------------------------------------

             Summary: Don't use ForkJoinPool#commonPool() for executing asynchronous operations
in Fabric8FlinkKubeClient
                 Key: FLINK-15791
                 URL: https://issues.apache.org/jira/browse/FLINK-15791
             Project: Flink
          Issue Type: Sub-task
          Components: Deployment / Kubernetes
    Affects Versions: 1.10.0
            Reporter: Till Rohrmann
             Fix For: 1.11.0, 1.10.1


We should not use the {{ForkJoinPool#commonPool()}} in order to run asynchronous operations
in the {{Fabric8FlinkKubeClient}} as it is done [here|https://github.com/apache/flink/blob/master/flink-kubernetes/src/main/java/org/apache/flink/kubernetes/kubeclient/Fabric8FlinkKubeClient.java#L315].
Since we don't know which other component is using this pool, it can be quite dangerous to
use it as there might be congestion.

Instead, I propose to provide an explicit I/O {{Executor}} which is used for running asynchronous
operations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message