Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[improve] [client] Merge lookup requests for the same topic #21232

Merged
merged 1 commit into from
Sep 22, 2023

Conversation

poorbarcode
Copy link
Contributor

Motivation

Multiple consumers and producers can be maintained by the same Pulsar Client. In some cases, multiple consumers or producers might attempt to connect to the same topic. To optimize the process, it is recommended to perform the topic lookup only once for each topic.

Modifications

  • Merge lookup requests for the same topic.
  • Merge get partitioned metadata request for the same partitioned topic.

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository: x

@poorbarcode poorbarcode self-assigned this Sep 21, 2023
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Sep 21, 2023
@poorbarcode poorbarcode added this to the 3.2.0 milestone Sep 21, 2023
@poorbarcode poorbarcode added release/2.10.6 release/3.0.2 release/2.11.3 category/reliability The function does not work properly in certain specific environments or failures. e.g. data lost and removed doc-not-needed Your PR changes do not impact docs labels Sep 21, 2023
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Sep 21, 2023
@codecov-commenter
Copy link

Codecov Report

Merging #21232 (c641197) into master (66271e3) will increase coverage by 0.48%.
Report is 1 commits behind head on master.
The diff coverage is 100.00%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #21232      +/-   ##
============================================
+ Coverage     72.73%   73.22%   +0.48%     
- Complexity    32465    32506      +41     
============================================
  Files          1875     1887      +12     
  Lines        139929   140138     +209     
  Branches      15413    15428      +15     
============================================
+ Hits         101781   102616     +835     
+ Misses        30067    29438     -629     
- Partials       8081     8084       +3     
Flag Coverage Δ
inttests 24.15% <95.45%> (-0.03%) ⬇️
systests 24.72% <100.00%> (?)
unittests 72.54% <100.00%> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
...e/pulsar/client/impl/BinaryProtoLookupService.java 80.42% <100.00%> (+2.90%) ⬆️

... and 158 files with indirect coverage changes

@poorbarcode poorbarcode merged commit be4ab66 into apache:master Sep 22, 2023
poorbarcode added a commit that referenced this pull request Sep 24, 2023
Motivation: Multiple consumers and producers can be maintained by the same Pulsar Client. In some cases, multiple consumers or producers might attempt to connect to the same topic. To optimize the process, it is recommended to perform the topic lookup only once for each topic.

Modifications:
- Merge lookup requests for the same topic.
- Merge get partitioned metadata request for the same partitioned topic.

(cherry picked from commit be4ab66)
poorbarcode added a commit that referenced this pull request Sep 24, 2023
Motivation: Multiple consumers and producers can be maintained by the same Pulsar Client. In some cases, multiple consumers or producers might attempt to connect to the same topic. To optimize the process, it is recommended to perform the topic lookup only once for each topic.

Modifications:
- Merge lookup requests for the same topic.
- Merge get partitioned metadata request for the same partitioned topic.

(cherry picked from commit be4ab66)
poorbarcode added a commit that referenced this pull request Sep 24, 2023
Motivation: Multiple consumers and producers can be maintained by the same Pulsar Client. In some cases, multiple consumers or producers might attempt to connect to the same topic. To optimize the process, it is recommended to perform the topic lookup only once for each topic.

Modifications:
- Merge lookup requests for the same topic.
- Merge get partitioned metadata request for the same partitioned topic.

(cherry picked from commit be4ab66)
Technoboy- pushed a commit that referenced this pull request Sep 25, 2023
Motivation: Multiple consumers and producers can be maintained by the same Pulsar Client. In some cases, multiple consumers or producers might attempt to connect to the same topic. To optimize the process, it is recommended to perform the topic lookup only once for each topic.

Modifications:
- Merge lookup requests for the same topic.
- Merge get partitioned metadata request for the same partitioned topic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants