Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Enhancing GlueTransform Stage for Stepfunction Crawler Task Retry #206

Closed
anmolsgandhi opened this issue Jan 11, 2023 · 0 comments · Fixed by #208
Closed

Enhancement: Enhancing GlueTransform Stage for Stepfunction Crawler Task Retry #206

anmolsgandhi opened this issue Jan 11, 2023 · 0 comments · Fixed by #208
Assignees
Labels

Comments

@anmolsgandhi
Copy link
Collaborator

Is your idea related to a problem? Please describe.

  • In its current state, the crawler step catches the failure if the crawler is already running and still goes ahead with a success flag. In alot of customer situations where a crawler is involved, a success state when crawler was already running where the step function task failed will not guarantee the next process gets the most recent data in the data catalog. In current state, even though we have alarms for the step function, it will hardly be in alarm state for crawler task as we are succeeding it by design.

Describe the solution you'd like
A clear and concise description of what you want to happen.

  • We can add retries and backoff for the crawler task in step function so that it tries multiple time before failing it, also we should allow for it to fail if the crawler throws exception after all retries as that will allow CloudWatch to capture right metrics for alarm.

P.S. Don't attach files. Please, prefer add code snippets directly in the message body.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants