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

[azeventhubs] Processor optimization to not list checkpoints when no ownership changes #22783

Open
PaulBernier opened this issue Apr 25, 2024 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@PaulBernier
Copy link

Feature Request

I noticed that in the Processor#dispatch function, that is called every 10s by default, all the checkpoints are being fetched but during most of the time (i.e. when no ownership is being re-shuffled) those checkpoints end up just not being used. There is an opportunity to save a lot of calls to the checkpoint store, and save $. Could it be optimized so checkpoints are only fetched when necessary?

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. labels Apr 25, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl.

@jhendrixMSFT jhendrixMSFT removed the Service Attention This issue is responsible by Azure service team. label Apr 26, 2024
@github-actions github-actions bot added the needs-team-triage This issue needs the team to triage. label Apr 26, 2024
@jhendrixMSFT jhendrixMSFT removed the needs-team-triage This issue needs the team to triage. label Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants