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

Log information about memory limit #7160

Merged
merged 4 commits into from
Oct 19, 2022
Merged

Conversation

fjetter
Copy link
Member

@fjetter fjetter commented Oct 19, 2022

I think the decisions we're making here are sane but it may still be surprising for users so I think emitting a couple of logs is useful.

Closes #7155

Copy link
Member

@jrbourbeau jrbourbeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @fjetter. Just a couple of minor comments. Overall this looks like a nice improvement

distributed/worker_memory.py Outdated Show resolved Hide resolved
distributed/worker_memory.py Show resolved Hide resolved
@github-actions
Copy link
Contributor

github-actions bot commented Oct 19, 2022

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       15 files  ±0         15 suites  ±0   5h 59m 17s ⏱️ - 22m 59s
  3 150 tests +1    3 065 ✔️ +  7    85 💤 ±0  0  - 6 
23 307 runs  +8  22 394 ✔️ +16  913 💤  - 2  0  - 6 

Results for commit dc3dd47. ± Comparison against base commit ec00cd5.

♻️ This comment has been updated with latest results.

@jrbourbeau jrbourbeau merged commit 8899e3c into dask:main Oct 19, 2022
@fjetter fjetter deleted the memory_limit_logging branch October 21, 2022 08:41
gjoseph92 pushed a commit to gjoseph92/distributed that referenced this pull request Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LocalCluster does not respect memory_limit keyword when it is large
2 participants