Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

aws glue import-catalog-to-glue still pending after 3 weeks

0

We received a notification that we are using deprecated Amazon Athena APIs or use a deprecated Athena data catalog resource. (In this case, it appears to be a data catalog)

Using the information provided, I went into the AWS CLI and used the following command with the appropriate region and catalog ID:

aws glue import-catalog-to-glue --region {region} --catalog-id {catalogId}

My expectation was that it would take a little time to run completely, as it's not a small data catalog, but it's not a large one either. However, it has been, at this point, a few weeks, and it still shows as "Pending" in the AWS Health Dashboard.

Is there some step that I missed, or something that I need to do regarding the data catalog to get this change to go through? For instance, if this was an EC2 database, I might expect to have to stop the database, run the above command, and restart the database, but there does not appear to be any such function regarding an Athena data catalog.

Any help would be greatly appreciated.

Topics
Analytics
Tags
AWS GlueAmazon Athena
Language
English

asked 2 years ago326 views

1 Answer
1

The situation you're experiencing with the import-catalog-to-glue operation taking an unusually long time is not typical. The migration process from an Athena Data Catalog to AWS Glue should not take weeks to complete. Here are some steps you can take to address this issue:

  1. Check the status of the migration: Use the AWS Glue API or CLI to check the status of the migration. You can use the GetCatalogImportStatus operation to retrieve the current status of the migration. This will give you more detailed information about whether the migration has completed or if there are any issues.

  2. Verify the catalog ID: Ensure that you're using the correct catalog ID in your command. The catalog ID should be your AWS account ID.

  3. Check for errors: Look for any error messages in the AWS Glue console or CloudWatch logs. There might be specific issues preventing the migration from completing.

  4. Contact AWS Support: If the migration is still showing as pending after several weeks, it's advisable to contact AWS Support. They can investigate why the process is taking so long and help resolve any underlying issues.

  5. Consider re-running the migration: If there are no active processes and you've verified there are no errors, you might want to try running the import-catalog-to-glue command again.

Regarding your question about stopping or restarting the catalog - unlike EC2 instances, there's no need to stop or restart an Athena data catalog for this migration process. The import should be able to run without interrupting your ability to query data.

If you continue to face issues, it's best to reach out to AWS Support for personalized assistance, as they can access account-specific information and provide more targeted troubleshooting.
Sources
Importing an Athena catalog to AWS Glue - AWS Glue
ImportCatalogToGlue - AWS Glue
CatalogImportStatus - AWS Glue

answered 2 years ago

EXPERT

reviewed 2 years ago

  • PGearman
    2 years ago

    I used "aws glue get-catalog-import-status --catalog-id" with the appropriate catalog ID in the CLI and it said the import status was complete, (ImportCompleted: true) but it's still showing as Pending in the Health Dashboard.

    Please advise as to how the Health Dashboard can be updated to reflect that, and so we stop receiving messages from AWS that this needs to be done.

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.

Relevant content