Limit vault blob broadcast concurrency

[prashantkumar1982]

Summary

• Ports the Vault blob broadcast concurrency limit from Limit vault blob broadcast concurrency #22239 to release/2.41.1.
• Limits observation blob broadcasts to at most 10 in-flight calls so large pending queues do not create unbounded goroutine fan-out during an OCR round.
• Keeps the existing per-blob timeout and skip-on-individual-failure behavior while preserving fast propagation for parent context cancellation or deadline expiry.
• Adds a regression test that holds broadcasts open and verifies concurrency stays within the configured limit.

[github-actions]

✅ No conflicts with other open PRs targeting release/2.41.1

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs