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.
[Feature Request] Migrate gRPC transport executor to ForkJoinPool for improved performance · opensearch-project/OpenSearch#19370 | Good First Issue