worker: tolerate transient triton health check failures - #82
Open
haraschax wants to merge 1 commit into
Open
Conversation
When triton is briefly unreachable, check_triton_server_health raises after its tenacity retry (15s). The worker re-raised this, crashing the job; slurm's --requeue then restarted it in a tight loop, dumping a full traceback to the per-job log on every cycle. A single downed triton server could grow /var/log/slurm/miniray-worker.*.log to tens of GB and fill the node's disk. Instead, log a concise line and continue the loop. The worker stays alive and retries triton on the next iteration (with the existing backoff), resuming work once triton recovers.
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.
No description provided.