Running shutdown is suboptimal

mariokostelac / sagemaker-knockout

🥊 Automatic shutdown for SageMaker instance when it's not active!

MIT License

9 stars 1 forks source link

Running shutdown is suboptimal #1

Closed mariokostelac closed 5 years ago

mariokostelac commented 5 years ago

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.

mariokostelac commented 5 years ago

Seems that current notebook instance name can be found in /etc/opt/ml/jobs/job.json.

mariokostelac commented 5 years ago

This issue is fixed by the commit referenced above.