[FLINK-17024] Make AkkaRpcService#getExecutor return a custom thread pool

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: Runtime / Coordination
• Assignee: Unassigned
• Reporter: Yang Wang
• Created: 07/Apr/20 10:02
• Updated: 12/Feb/21 14:23
• Resolved: 12/Feb/21 14:15

Description

Follow the discussion in this PR[1].

Currently, AkkaRpcServcie#getExecutor returns Akka's underlying dispatcher thread pool. It should not be used since it will take the risk to affect the main thread of rpc endpoint. We could return a custom thread pool instead. The it is safe to used for some I/O operations  in the RpcEndpoint, for example, stopPod in KubernetesResourceManager. An elastic thread pool(from 4 up to 16) is enough.

 

[1]. https://github.com/apache/flink/pull/11427#discussion_r402738678

Issue Links

• is superceded by: FLINK-21368 Remove RpcService#getExecutor