Receiving EntityNotFoundException error intermittently

0

Hello everyone, We have been receiving this EntityNotFoundException error intermittently for one of our lambda fuctions. We've found that the EntityNotFoundException error we've been getting is actually a result of the GLUE job not being processed properly, which is why it's failing. By looking at the logs, We can see that the GLUE job is having issue in creating new table after deleting the old one which is why the lambda function is not able to locate it. We need guidance on why the error is occuring as there have been no code changes from our side.

Error Details: [ERROR] EntityNotFoundException: An error occurred (EntityNotFoundException) when calling the GetTable operation: Table tbl_site_crowdflower not found. Traceback (most recent call last):   File "/var/task/lambda_function.py", line 104, in lambda_handler     create_generic_db(data,bus_date,src_bucket_name)   File "/var/task/lambda_function.py", line 146, in create_generic_db     res = glue.get_table(DatabaseName=backup_databasename, Name=tbl_name)   File "/var/runtime/botocore/client.py", line 391, in _api_call     return self._make_api_call(operation_name, kwargs)   File "/var/runtime/botocore/client.py", line 719, in _make_api_call     raise error_class(parsed_response, operation_name)

EntityNotFoundException

  • Are you creating and deleting the same table? I wonder if it's a timing issue.

asked a year ago199 views
1 Answer
0

Hello,

Based on the error message:

EntityNotFoundException: An error occurred (EntityNotFoundException) when calling the GetTable operation: Table tbl_site_crowdflower not found.

Looking into the stack trace, the exception was triggerred by this lineres = glue.get_table(DatabaseName=backup_databasename, Name=tbl_name) , which is a Glue get_table API call via boto3.

The exception indicates your boto3 client cannot find table "tbl_site_crowdflower". Such an issue can be caused by various reasons, please double check and make sure:

  1. The specific table exists under the database and the region.
  2. If your account has enabled Lake Formation permission control, check if the IAM role has sufficient Lake Formation permissions to list the database and the table.

I hope this helps resolve the issue. Have a nice day!

Ref: https://docs.aws.amazon.com/lake-formation/latest/dg/lf-permissions-reference.html https://docs.aws.amazon.com/lake-formation/latest/dg/granting-catalog-permissions.html

AWS
Ethan_H
answered a year 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