Fix NVMLError_Unknown: init NVML once, auto reset+retry on failure - #1
Open
tugrultamerc wants to merge 1 commit into
Open
Fix NVMLError_Unknown: init NVML once, auto reset+retry on failure#1tugrultamerc wants to merge 1 commit into
tugrultamerc wants to merge 1 commit into
Conversation
…efully The app called nvmlInit/nvmlShutdown on every request from multiple threadpool workers. After a host driver reload/update this left NVML in a bad state and /gpu returned 500 with NVMLError_Unknown. - Initialize NVML once per process (thread-safe), shutdown at exit - On NVMLError during gather: shutdown+re-init and retry once - On init failure: attempt one reset before giving up - Return schema-valid status=error payload instead of an unhandled 500 - Add smoke tests covering outage, recovery, and retry behavior
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
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 app called nvmlInit/nvmlShutdown on every request from multiple threadpool workers. After a host driver reload/update this left NVML in a bad state and /gpu returned 500 with NVMLError_Unknown.