By using AWS re:Post, you agree to the Terms of Use

AWS Glue "Task allocated capacity exceeded limit" solved but error persist at notebook session creation

2

Yesterday we had the error Failed to start notebook server "Task allocated capacity exceeded limit. (Service: AWSGlueJobExecutor; Status Code: 400; Error Code: InvalidInputException)" caused by Max task dpus per account quota defined as 0 internally by AWS. Once it was fixed by returning it to its default value following documentation, ETLs are able to run but the error persist at notebook session creation:

Exception encountered while creating session: An error occurred (ResourceNumberLimitExceededException) when calling the CreateSession operation: Failed to meet resource limits for operation

botocore.errorfactory.ResourceNumberLimitExceededException: An error occurred (ResourceNumberLimitExceededException) when calling the CreateSession operation: Failed to meet resource limits for operation

Increasing the limits of Max concurrent job runs per account and Max task dpus per account has not solved the error

asked 24 days ago150 views
1 Answers
0

I have also got same error. Apparently this is bug from AWS side, raised a Ticket to AWS support and they increased the limit from backend. Below is the response from AWS Support:

"We have reset the value for "max-interactive-sessions" from 0 to the default which is 100. Unfortunately this value recently got changed due to a bug on the AWS side"

answered 14 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions