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

Get rid of error message after COG jobs successfully complete. #159

Merged
merged 2 commits into from
Oct 3, 2024

Conversation

danscales
Copy link
Contributor

Get rid of error message after COG jobs successfully complete.

Even when the integrated alerts COG jobs successfully complete, there is a data-updates error message. It turns out this is because we didn't increase the integrated_alerts job timeout when we added the very long extra COG steps. The final cogify step completes, but a timeout error is still reported. So, I just added an extra 7 hours to the timeout for IntegratedAlertsSync job.

Even when the integrated alerts COG jobs successfully complete, there is
a data-updates error message. It turns out this is because we didn't
increase the integrated_alerts job timeout when we added the very long
extra COG steps. So, I just added an extra 7 hours to the timeout for
IntegratedAlertsSync job.
We seem to seem to get a ThrottlingException on describe_cluster()
fairly often (often happens several time every couple of nights). This
causes the entire job process to fail (or at least not finish the
post-processing). So, I'm adding a few retries if we get a ClientError
which is a ThrottlingException on the describe_cluster() call in
check_analysis().
@danscales danscales merged commit b575044 into develop Oct 3, 2024
3 checks passed
@danscales danscales deleted the raise-cogify-timeout branch October 3, 2024 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants