-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Cleanup AWS EC2 eventual consistency warnings #9637
Cleanup AWS EC2 eventual consistency warnings #9637
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
159c185
to
0876165
Compare
Good question whether we prefer the individual tasks to sleep or letting the task scheduler retry after a delay. |
The task already retries until it succeeds, but the problem is the useless warnings. Unless there is a way to tell the task just to retry and not print a warning, seems best to keep this logic in each individual task. |
/retest |
We could create a new type which, if embedded in an |
07ea166
to
75c5c34
Compare
|
||
if awsup.AWSErrorCode(err) == "ValidationError" { | ||
message := awsup.AWSErrorMessage(err) | ||
if strings.Contains(message, "not authorized") || strings.Contains(message, "Invalid IamInstance") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I never seen these warnings in my tests. Would like to see if the handling for these errors is still needed.
I think it should be better now.
|
/retest |
75c5c34
to
d4dcf3e
Compare
c7b0d46
to
4c04a65
Compare
/retest |
4c04a65
to
3da7927
Compare
/retest |
/assign @johngmyers |
3da7927
to
3a11207
Compare
/lgtm |
When a cluster is created, there are warnings such as:
This happens because of AWS EC2 eventual consistency issues:
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#eventual-consistency