- Mais recentes
- Mais votos
- Mais comentários
Thank you for providing these specifics. I'm curious to know whether this issue occurs intermittently or if it consistently takes more than 30 seconds to yield results. Assuming the current architecture follows a 'client - Cloudflare - ELB - application' pattern, an unusually prolonged 'Transfer Start' time could imply a delay in the 're-connection' to the ELB, more than what we'd typically expect.
If this is an intermittent issue, it's possible that one of the ELB nodes resides in a private subnet. This would cause a connection timeout when Cloudflare attempts to connect to the ELB node's IP within this private subnet. However, if Cloudflare subsequently attempts to connect to a different IP, it should then succeed. Could this potentially be the root cause of the problem? Read this document for further explanation.
Otherwise, diving into the Cloudflare logs should also shed some light moving forward.
We made sure that the ELB node was within a public subnet within the VPC. The delay was noticeable consistently through all requests for both applications. The test we were conducting was using a PostgreSQL add-on database instance from a Heroku deployment in the eu
region (our first demo was using the existing production database to test beanstalk app server workloads independently before shifting the DB as well to RDS in the next stage) under the assumption that the underlying EC2s were using the eu-central-1
region. After tracing the public Heroku endpoint IP address to find its location, it turned out to be eu-west-1
in Dublin, and it appears this was the cause of the issue
Thank you for your cooperation @weidi
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 9 meses
- Como posso carregar arquivos do WordPress maiores que 2 MB para o meu ambiente do Elastic Beanstalk?AWS OFICIALAtualizada há 7 meses