opensearch-project/OpenSearch

[Feature Request] Migrate gRPC transport executor to ForkJoinPool for improved performance

Open

#19,370 建立於 2025年9月22日

在 GitHub 查看
 (2 留言) (0 反應) (2 負責人)Java (8,123 star) (1,505 fork)batch import
Search:Performanceenhancementgood first issue

描述

Is your feature request related to a problem? Please describe

The gRPC transport currently uses a FixedExecutorBuilder for processing gRPC service calls. While this provides significant improvements over the previous directExecutor() approach, ForkJoinPool would offer even greater performance benefits, such as better load balancing through built-in mechanisms like work-stealing.

Describe the solution you'd like

Once PR #19008 to add ForkJoinPool support is merged, the gRPC transport should migrate from using FixedExecutorBuilder to ForkJoinPoolExecutorBuilder.

Related component

Search:Performance

Describe alternatives you've considered

No response

Additional context

No response

貢獻者指南

技術棧
java
領域
performancesearch
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java concurrency knowledgegRPC basicsFamiliarity with OpenSearch codebase
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue depends on PR #19008 (adding ForkJoinPool support) which must be merged first. After that, the changes involve modifying the gRPC transport configuration in files such as opensearch/src/main/java/org/opensearch/transport/grpc/. The migration from FixedExecutorBuilder to ForkJoinPoolExecutorBuilder should be done as described. There are two assignees, indicating active work or intent. Check comments for additional context.