Skip to content

[exporterhelper] Do not ignore the num_consumers setting when batching is enabled #12921

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

Merged

Conversation

dmitryax
Copy link
Member

Remove hardcoding the number of queue workers to one if batching is enabled. The bug described in #12244 isn't relevant anymore.

@dmitryax dmitryax requested review from bogdandrutu and a team as code owners April 25, 2025 04:54
@dmitryax dmitryax changed the title Do not ignore the num_consumers setting when batching is enabled [exporterhelper[ Do not ignore the num_consumers setting when batching is enabled Apr 25, 2025
@dmitryax dmitryax changed the title [exporterhelper[ Do not ignore the num_consumers setting when batching is enabled [exporterhelper] Do not ignore the num_consumers setting when batching is enabled Apr 25, 2025
Copy link

codecov bot commented Apr 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.66%. Comparing base (ac7c0f2) to head (0d1d2bc).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #12921      +/-   ##
==========================================
- Coverage   91.66%   91.66%   -0.01%     
==========================================
  Files         499      499              
  Lines       27426    27425       -1     
==========================================
- Hits        25141    25140       -1     
  Misses       1806     1806              
  Partials      479      479              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bogdandrutu
Copy link
Member

bogdandrutu commented Apr 25, 2025

I saw your comment about sending batches, that is already distributed if I am not mistaken, and it always create a new goroutine for exporting

@dmitryax
Copy link
Member Author

@bogdandrutu it is distributed but limited by the number of workers which is set to the num_consumers. Let me know if I miss something

@bogdandrutu
Copy link
Member

You are right this is a bug, we should set num consumers after initialization of the batch to 1… need to push this asap

Remove hardcoding the number of queue workers to one if batching is enabled. The bug described in open-telemetry#12244 isn't relevant anymore.
@dmitryax dmitryax force-pushed the batciher-remove-workers-restriction branch from f42b88e to 0d1d2bc Compare April 25, 2025 16:44
@github-actions github-actions bot requested a review from bogdandrutu April 25, 2025 16:44
@bogdandrutu bogdandrutu enabled auto-merge April 25, 2025 16:55
@bogdandrutu bogdandrutu added this pull request to the merge queue Apr 25, 2025
Merged via the queue into open-telemetry:main with commit f26c6bb Apr 25, 2025
56 checks passed
@dmitryax dmitryax deleted the batciher-remove-workers-restriction branch April 25, 2025 18:49
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