-
Notifications
You must be signed in to change notification settings - Fork 227
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
Topic creation fails with DEADLINE_EXCEEDED error #1414
Comments
It looks like this was recently changed as the Node.js client library had different default settings compared to the other languages, which made debugging difficult: #1399 is the relevant change. Let me tag in the author of that PR @feywind to see if there is a way to override this (I think there is but I am not certain). |
Yeah, we changed these defaults to be in line with some other services. Maybe @kamalaboulhosn can speak to the reasoning behind those changes? (Or if I did them incorrectly...) In the meantime, I think you should be able to override them with something like this:
When I try that, I get this from grpc-js:
|
@feywind The intention was for the change to 5 seconds to only affected Publish calls, not CreateTopic calls. CreateTopic should have a deadline of 60s. |
Eep, thanks for the clarification. I'll see if I can move the change to just Publish. |
+1 same issue |
Got the same issue. |
i have the same issue. downgrade to v2.17.0 solve my issue |
We create topics like this
It was working fine before but started failing with DEADLINE_EXCEEDED error after we updated to the latest version 2.18.1.
We enabled gRPC debug mode and saw that all gRPC requests are sent with grpc-timeout header close to 5sec. After 5 seconds we get the error.
We checked with older version 2.8.0 and the grpc-timeout header is equal to 60 seconds. And topics were created fine. And it seems it also takes arount 5sec to create a topic. Looks like smth was changed between theses two version.
We tried to pass timeout attribute in topic.create method but it did not make any difference. Is there any way to increase/override the grpc-timeout value?
The text was updated successfully, but these errors were encountered: