apache/pulsar

Cleanup synchronous call in resources component

Open

#22,544 opened on Apr 20, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (13,697 stars) (3,485 forks)batch import
help wantedtype/enhancement

Description

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!

Contributor guide

Tech stack
java
Domain
backendperformance
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaAsynchronous programmingPulsar resources component
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.
Cleanup synchronous call in resources component · apache/pulsar#22544 | Good First Issue