You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
Some indexes are created, the others are giving this error:
Error: Error creating Index: googleapi: Error 409: Aborted due to cross-transaction contention. This occurs when multiple transactions attempt to access the same data, requiring Firestore to abort at least one in order to enforce serializability.
It seems like the provider should retry on this error too.
Steps to Reproduce
Run terraform apply.
Important Factoids
References
#0000
The text was updated successfully, but these errors were encountered:
raz-amir
changed the title
Creating multiple indexes in firestore in datastore modes may lead to: Error 409: Aborted due to cross-transaction contention
Creating / deleting multiple indexes in firestore in datastore modes may lead to: Error 409: Aborted due to cross-transaction contention
Nov 23, 2023
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform: 1.6.4
Google provider: 5.7.0
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/ramir-savvy/622c116aae0ef6de01bb9b7356b1839a
Panic Output
Expected Behavior
All indexes should be created
Actual Behavior
Some indexes are created, the others are giving this error:
It seems like the provider should retry on this error too.
Steps to Reproduce
Run
terraform apply
.Important Factoids
References
The text was updated successfully, but these errors were encountered: