Redis connect ETIMEDOUT error with Direct VPC egress

Hello,

We have multiple Cloud Run services that have started using the Direct VPC for Redis connection, however, yesterday there were two Cloud Run services that had the ETIMEDOUT error. One service had that incident so we have to switch back to the VPC connector for now.

- A service incident from November 2nd, 04:13pm - 05:43pm EST – customer facing, we have to switch back to VPC connector, once that was switched and the incident stopped
- B service incident from November 2nd, 8:40pm - 10:03pm EST
- All other services have no ETIMEDOUT errors

At the current preview stage, anywhere we can see the direct VPC egress status? or anyone know what may happen during the above time frames?  Thanks

1 2 566
2 REPLIES 2

Hi @weizhong-sk,

Welcome to Google Cloud Community!

The Google Cloud team is aware of the Direct VPC egress issue and is working on a fix. There is currently no publicly available way to see the status of Direct VPC egress.

There are a few possible explanations for the ETIMEDOUT errors:

  • A temporary network issue.
  • A bug in the Direct VPC egress feature.
  • A problem with the Redis configuration or implementation.

To troubleshoot the issue, you can try the following:

  • Check the Cloud Run logs for more information about the errors.
  • Try connecting to Redis from a different Cloud Run service or from a machine outside of Cloud Run.
  • Try restarting the Cloud Run services that are experiencing the errors.
  • Try disabling and then re-enabling Direct VPC egress on the affected services.

You may contact Google Cloud support for assistance.

In the meantime, you may want to switch back to using the VPC connector for the affected services.

Hi,

we are affected by the same issue currently. Interestingly enough though, we only experience the issue for a couple of hours in the morning until around 12 noon (CET) which is kind of weird.

"The Google Cloud team is aware of the Direct VPC egress issue and is working on a fix"
-> Will you post a comment here once this has been resolved?

Best,
Patrick