-
Notifications
You must be signed in to change notification settings - Fork 592
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
Cloud Secrets Manager often errors DEADLINE Exceeded #5043
Comments
My most recent logs:
The pattern I am using: const secret = await getSecretFromGCloud() // this takes 10 seconds
axios.post(url, payload, headers) |
Same problem here 😞 |
Anyone from gcloud know if this is just a region issue? It's severely critical My settings:
|
I have the same problem. Loading a secret takes ~10 seconds for me. The weird thing is that it's only slow for me, not my colleagues, even though we're on the same network, hardware etc. |
I also seem to experience the same problem. I have an express.js app which tries to retrieve some secrets |
happening here |
how do you manage to use secrets in a cloud function in case of cold start? |
⏳
Secrets Manager retrieved in 31.092 seconds
So slow!
Yes I have tried the quick fixes and google cloud docs & github/stackoverflow search.
Environment details
Steps to reproduce
About 25% of the time, cloud secrets manager will timeout when attempting to access a secret. I have logged avg duration to get a secret and its around 10-30 seconds on first attempt (and <1 sec thereafter). The code is run within firebase functions and cloud run on us-central1. All my secrets managers are set to auto-replication policy.
What is causing this issue and how can I fix it? It's severely critical.
The pattern I am using:
Error:
Error: 4 DEADLINE_EXCEEDED: Deadline exceeded
at callErrorFromStatus (/workspace/node_modules/@google-cloud/secret-manager/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
at Object.onReceiveStatus (/workspace/node_modules/@google-cloud/secret-manager/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
at Object.onReceiveStatus (/workspace/node_modules/@google-cloud/secret-manager/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
at Object.onReceiveStatus (/workspace/node_modules/@google-cloud/secret-manager/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
at /workspace/node_modules/@google-cloud/secret-manager/node_modules/@grpc/grpc-js/build/src/resolving-call.js:99:78
at processTicksAndRejections (node:internal/process/task_queues:77:11)
at runNextTicks (node:internal/process/task_queues:64:3)
at process.processTimers (node:internal/timers:509:9)
The text was updated successfully, but these errors were encountered: