opensearch-project/OpenSearch

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

Open

#19,370 opened on 2025年9月22日

GitHub で見る
 (2 comments) (0 reactions) (2 assignees)Java (8,123 stars) (1,505 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.