Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
zombie processes from dvc pull failures
See original GitHub issuePlease provide information about your setup
DVC version(i.e. dvc --version), Platform and method of installation (pip, homebrew, pkg Mac, exe (Windows), DEB(Linux), RPM(Linux))
DVC version 0.93.0 Platform: DGX2 kubernetes cluster, installation with pip,
The base image we use.
FROM nvcr.io/nvidia/pytorch:19.10-py3
When we call dvc pull, if the pull fails for any reason (lack of right credentials for one, or if we ctr-C), we see a lot of zombie processes start spawning on our pod. This occurs to the point that it ties up all free resources on the cluster and grinds things to a halt. Can someone look into this please? It’s affecting a pilot team promoting DVC usage at a major healthcare corporation.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ychou85 could please run
ps -aef | grep dvcor something similar to get fulldvccommands with arguments, to actually see what is running now.@ychou85 could you please try to opt-out from the analytics as described here - https://dvc.org/doc/user-guide/analytics ?
@efiop can it be updater daemon also?