1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Typically lifecycle configuration scripts will timeout > 5 minutes. So if you're not seeing this timeout it could be something else that is causing the notebook to take 20 minutes to start. Check out the logs to see if you can pinpoint the issue as mentioned by another user: https://docs.aws.amazon.com/sagemaker/latest/dg/jupyter-logs.html
Instead of building a custom container image this is our published best practice to improve lifecycle configuration script time: https://aws.amazon.com/premiumsupport/knowledge-center/sagemaker-lifecycle-script-timeout/
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
Can you tell whether it's taking 20 mins to start an instance or to run your lifecycle configuration?
Please check Jupyter notebook logs in cloudwatch at the duration of booting of your notebook instance. It will give the right indicators, what's happening and cause of delay. https://docs.aws.amazon.com/sagemaker/latest/dg/jupyter-logs.html Check out Lifecycle configuration best practices => https://docs.aws.amazon.com/sagemaker/latest/dg/nbi-lifecycle-config-install.html