1 Answer
- Newest
- Most votes
- Most comments
0
This typically happens when there's high resource utilization on the notebook instance and increasing instance type may help. Additionally, I would suggest that you open a support case under SageMaker queue by providing Sagemaker notebook ARN and associated Cloudwatch logs recorded for this notebook so that a support engineer can further troubleshoot the issue.
answered 2 years ago
Relevant content
- Accepted Answer
- asked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
maybe it is possible that you overrun memory?