Skip to content

[Datasets] Tie _DesignatedBlockOwner lifetime to context creator#22007

Merged
ericl merged 1 commit intoray-project:masterfrom
clarkzinzow:datasets/fix/designated-block-owner-leak
Feb 1, 2022
Merged

[Datasets] Tie _DesignatedBlockOwner lifetime to context creator#22007
ericl merged 1 commit intoray-project:masterfrom
clarkzinzow:datasets/fix/designated-block-owner-leak

Conversation

@clarkzinzow
Copy link
Copy Markdown
Contributor

Instead of using a detached lifetime, tie the lifetime of _DesignatedBlockOwner to the lifetime of the context creator. Also, only create a _DesignatedBlockOwner if dynamic block splitting is enabled.

Related issue number

Closes #21999

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

…esignatedBlockOwner if dynamic block splitting is enabled.
@ericl ericl added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Jan 31, 2022
@clarkzinzow clarkzinzow added tests-ok The tagger certifies test failures are unrelated and assumes personal liability. and removed @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. labels Feb 1, 2022
@clarkzinzow
Copy link
Copy Markdown
Contributor Author

Datasets tests pass, ready to merge.

@ericl ericl merged commit 00e1ac3 into ray-project:master Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests-ok The tagger certifies test failures are unrelated and assumes personal liability.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Datasets] [Bug] workers and actors leaking in trivial dataset use

3 participants