[Data] Deprecate ConcurrencyCapBackpressurePolicy#63392
Merged
bveeramani merged 4 commits intoMay 18, 2026
Conversation
Mark ConcurrencyCapBackpressurePolicy as deprecated with a removal target of Ray 2.59. Emits a RayDeprecationWarning on instantiation. Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
Contributor
There was a problem hiding this comment.
Code Review
This pull request deprecates the ConcurrencyCapBackpressurePolicy class by applying the @deprecated decorator. The reviewer suggested enhancing the deprecation message by including a recommended replacement policy to provide a clear migration path for users.
Emit the deprecation warning conditionally (only when enable_dynamic_output_queue_size_backpressure is set), and add unit tests for both the enabled and disabled cases. Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f777ca4. Configure here.
Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
richardliaw
approved these changes
May 18, 2026
TruongQuangPhat
pushed a commit
to cyhapun/ray-fix-issue
that referenced
this pull request
May 27, 2026
We introduced an experimental "dynamic queue size backpressure" six months ago in ray-project#57996. This PR adds a warning that we're going to deprecate it in a few releases. We've decided to deprecate it for a couple reasons: * It's hard to understand. The policy requires ~400 lines of control logic with multiple tunable constants, trend detection across two different signals (percentage growth and absolute growth), and sliding window history tracking. * It performed worse than the simpler `DownstreamCapacityBackpressurePolicy` in our experiments. * Removing the policy allows us to simplify the `ResourceManager` interface. `ResourceManager` is one of Ray Data's most involved modules. --------- Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu> Signed-off-by: phattruong <23120318@student.hcmus.edu.vn>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

We introduced an experimental "dynamic queue size backpressure" six months ago in #57996.
This PR adds a warning that we're going to deprecate it in a few releases.
We've decided to deprecate it for a couple reasons:
DownstreamCapacityBackpressurePolicyin our experiments.ResourceManagerinterface.ResourceManageris one of Ray Data's most involved modules.