-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add retries for operations to account for intermittent network issues #6628
Comments
Signed-off-by: Modular Magician <magic-modules@google.com>
This issues seems to have two parts:
We still have some work to do with retrying transient error, but application level retry should be sufficient. Handling already_exists error might be something we can do. I think it was something like this:
In GoogleCloudPlatform/magic-modules#6735, we will remove the resource only if there is a NOT_FOUND error. This should prevent the resources being cleared on transient errors (or any error other than NOT_FOUND). |
b/259278591 |
We have more work to do in term of error handling. However, with GoogleCloudPlatform/magic-modules#6735, we don't clear the resource on errors other than NOT_FOUND. This should fix the reported problem. We should close this issue if no objection. |
Closing the issue - if there are additional similar issues please open a new ticket. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
Currently resource for instance creation or table creation for Bigtable resources do not seem to rely on retrying requests to account for intermittent network failures.
Consider a Terraform task to setup a bigtable instance with column family configuration. This results in multiple requests, and if additional requests fail, it results in complete task failure. Moreover, to complete the task involves having to delete the tables manually, as task fails due to since the table already exists.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: