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

Make AkkaRpcService#getExecutor return a custom thread pool

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment