Skip to content
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

[BUG] Release inactive dask futures #2657

Closed
jnke2016 opened this issue Sep 2, 2022 · 0 comments · Fixed by #2659
Closed

[BUG] Release inactive dask futures #2657

jnke2016 opened this issue Sep 2, 2022 · 0 comments · Fixed by #2659
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jnke2016
Copy link
Contributor

jnke2016 commented Sep 2, 2022

Describe the bug
The PLC algos leveraging the PLC graph were intermittently failing when running iteratively. This is due to dask failing to release all the inactive futures before the next iteration. A temporary solution was found by explicitly deleting the variable holding those futures and a FIXME was added.

@jnke2016 jnke2016 added ? - Needs Triage Need team to review and classify bug Something isn't working labels Sep 2, 2022
@jnke2016 jnke2016 changed the title [BUG] Release inactive dask future [BUG] Release inactive dask futures Sep 2, 2022
@rlratzel rlratzel added this to the 22.10 milestone Sep 2, 2022
@rapids-bot rapids-bot bot closed this as completed in #2659 Sep 5, 2022
rapids-bot bot pushed a commit that referenced this issue Sep 5, 2022
This is a follow up PR to wait for all the inactive futures to be released
closes #2657

Authors:
  - Joseph Nke (https://github.com/jnke2016)

Approvers:
  - Brad Rees (https://github.com/BradReesWork)
  - Rick Ratzel (https://github.com/rlratzel)

URL: #2659
@BradReesWork BradReesWork removed the ? - Needs Triage Need team to review and classify label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants