Skip to content

Fix to avoid exceeding concurrency in resource_limited_node#2103

Open
vossmjp wants to merge 1 commit into
masterfrom
dev/vossmjp/limiter_concurrency_fix
Open

Fix to avoid exceeding concurrency in resource_limited_node#2103
vossmjp wants to merge 1 commit into
masterfrom
dev/vossmjp/limiter_concurrency_fix

Conversation

@vossmjp

@vossmjp vossmjp commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Description

The max concurrency of a node is not controlled by its concurrency parameter but by the number of resources it can acquire. The execution of resource_limited_body_leaf was limited but that body only starts the async process to by calling request on the various providers and then returns. So the previous implementation guards the request logic not the body execution.

This PR releases the takes the concurrency slot in the body_leaf but only releases it when the body completes.

Fixes # - issue number(s) if exists

Type of change

Choose one or multiple, leave empty if none of the other choices apply

Add a respective label(s) to PR if you have permissions

  • bug fix - change that fixes an issue
  • new feature - change that adds functionality
  • tests - change in tests
  • infrastructure - change in infrastructure and CI
  • documentation - documentation update

Tests

  • added - required for new features and some bug fixes
  • not needed

Documentation

  • updated in # - add PR number
  • needs to be updated
  • not needed

Breaks backward compatibility

  • Yes
  • No
  • Unknown

Notify the following users

List users with @ to send notifications

Other information

@vossmjp vossmjp requested a review from kboyarinov June 3, 2026 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant