Running shutdown is suboptimal
mariokostelac opened this issue · comments
It seems that it takes some time for SageMaker to detect that instance is down after shutdown is run. Running aws sagemaker stop-notebook-instance seems more suitable for that.
Seems that current notebook instance name can be found in /etc/opt/ml/jobs/job.json.
This issue is fixed by the commit referenced above.