You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If for some reason the process immediately exits with non-zero exit code (often due to some failure condition or misconfiguration), it will be immediately restarted in a tight loop. This can load to high load and filling log files when things go wrong. It might be nice to either have some moderate delay before retrying, or a limit on how many time it can be restarted before giving up. Either of these could be configurable. The backoff logic used in ready wait could perhaps be reused somehow?
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
If for some reason the process immediately exits with non-zero exit code (often due to some failure condition or misconfiguration), it will be immediately restarted in a tight loop. This can load to high load and filling log files when things go wrong. It might be nice to either have some moderate delay before retrying, or a limit on how many time it can be restarted before giving up. Either of these could be configurable. The backoff logic used in ready wait could perhaps be reused somehow?
The text was updated successfully, but these errors were encountered: