apache/pulsar

Cleanup synchronous call in resources component

Open

#22,544 建立於 2024年4月20日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Java (13,697 star) (3,485 fork)batch import
help wantedtype/enhancement

描述

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

We should clean up all the synchronous call for resources components to avoid someone using them to block the metadata thread.

FYI: https://github.com/apache/pulsar/pull/22542

Solution

No response

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!

貢獻者指南

技術棧
java
領域
backendperformance
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaAsynchronous programmingPulsar resources component
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Examine the existing synchronous calls in the resources component. Refer to the linked PR #22542 for a similar cleanup pattern. Identify all places where synchronous calls are made that could block the metadata thread. Suggest converting them to asynchronous calls using the project's async framework. Ensure no regression in functionality.