hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.81k stars 9.16k forks source link

Timeout Errors Disassociating ElastiCache Replication Group from Global Replication Group #23583

Closed hfenton closed 6 months ago

hfenton commented 2 years ago

Community Note

Description

We are often seeing timeout errors disassociating ElastiCache Replication Group from Global Replication Group. There is currently not an option to override the current default of 20 minutes

module.oregon.module.redis_cache_secondary[0].aws_elasticache_replication_group.secondary_redis: Still destroying... [id=some-redis, 20m0s elapsed]
β•·
β”‚ Error: error disassociating ElastiCache Replication Group (some-redis) from Global Replication Group (fpkhr-global-redis): waiting for completion: timeout while waiting for resource to be gone (last state: 'associated', timeout: 20m0s)

https://github.com/hashicorp/terraform-provider-aws/blob/69a6ac89fe69e8ab45d3f024b31147560b36de2f/internal/service/elasticache/wait.go#L211-L225

New or Affected Resource(s)

Potential Terraform Configuration

resource "aws_elasticache_global_replication_group" "redis" {
  global_replication_group_id_suffix = "${var.env}-${var.application}-global-redis"
  primary_replication_group_id       = module.redis_cache.id

  timeouts {
    disassociate = "40m"
    create       = "30m"
    delete       = "20m"
    update       = "40m"
  }
}

References

github-actions[bot] commented 7 months ago

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

github-actions[bot] commented 5 months ago

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.