Repository navigation
Conversation
The worker table marked a worker red once its last heartbeat was more than 60s old, regardless of distributed.scheduler.worker-ttl. With the default 5 minute TTL that flags healthy-but-busy workers (e.g. ones holding the GIL) long before the scheduler would act, and users had no way to tune it. Color rows orange after 25% and red after 50% of the effective TTL, computed the same way as Scheduler.check_worker_ttl. When worker-ttl is disabled, keep the old 60s red threshold. Closes dask#8749 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 40 files ± 0 40 suites ±0 14h 6m 15s ⏱️ - 1m 27s For more details on these failures, see this check. Results for commit 2469b39. ± Comparison against base commit dc182bd. |
This branch has not been deployed
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
1 participant
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.
The worker table marked a worker red once its last heartbeat was more
than 60s old, regardless of distributed.scheduler.worker-ttl. With the
default 5 minute TTL that flags healthy-but-busy workers (e.g. ones
holding the GIL) long before the scheduler would act, and users had no
way to tune it.
Color rows orange after 25% and red after 50% of the effective TTL,
computed the same way as Scheduler.check_worker_ttl. When worker-ttl is
disabled, keep the old 60s red threshold.
pre-commiton the changed filesThis PR is a joint contribution from Nilanjan Chatterjee and Claude (Claude Opus 5.5, via Claude Code). Nilanjan chose the issue and directed the work; Claude reproduced the problem, wrote the change, its tests and this description.
Authored by Nilanjan Chatterjee (@nil68657).