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

Implement max concurrency to configure legacy behavior (1) or otherwise limit concurrency #254

Merged
merged 3 commits into from
Sep 25, 2024

Conversation

jmacd
Copy link
Contributor

@jmacd jmacd commented Sep 25, 2024

This adds a max_concurrency setting. When set to 0, concurrency is unlimited. When set to 1, behavior matches the legacy behavior of the core batch processor. When set to a value >1, this enables the user to artificially limit concurrency.

@jmacd jmacd merged commit b78f1ba into open-telemetry:main Sep 25, 2024
2 checks passed
@jmacd jmacd deleted the jmacd/max_conc branch September 25, 2024 21:47
@jmacd jmacd mentioned this pull request Sep 25, 2024
jmacd added a commit that referenced this pull request Sep 26, 2024
- Concurrent batch processor: concurrency limit for legacy behavior or
otherwise. [#254](#254)
- Concurrent batch processor: EarlyReturn legacy compat feature.
[#253](#253)
- Concurrent batch processor: Synchronize with upstream; removes
in-flight bytes metric,
removes panic recovery as unnecessary divergence.
[#251](#251)
- Update collector dependencies to v0.110.0/v1.16.0; remove validation
connector [#252](#252)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants