Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-17024

Make AkkaRpcService#getExecutor return a custom thread pool

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Runtime / Coordination
    • None

    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

      Attachments

        Issue Links

          is superceded by

          Improvement - An improvement or enhancement to an existing feature or task. FLINK-21368 Remove RpcService#getExecutor

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              wangyang0918 Yang Wang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: