Skip to content
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

Fix gRPC DeadlineExceeded error #2517

Closed
wants to merge 1 commit into from
Closed

Conversation

hansedong
Copy link

Mainly solves a large number of error logs that may appear in the drone-agent

grpc error: wait(): code: DeadlineExceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded

and the drone-server:

grpc: Server.processUnaryRPC failed to write status stream error: code = DeadlineExceeded desc = “context deadline exceeded”

Please see https://discourse.drone.io/t/fix-grpc-deadlineexceeded-error/2884 for futher information.

Mainly solves a large number of error logs that may appear in the drone-agent

`grpc error: wait(): code: DeadlineExceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded`

and the drone-server:

`grpc: Server.processUnaryRPC failed to write status stream error: code = DeadlineExceeded desc = “context deadline exceeded”`

Please see https://discourse.drone.io/t/fix-grpc-deadlineexceeded-error/2884 for futher information.
@CLAassistant
Copy link

CLAassistant commented Nov 5, 2018

CLA assistant check
All committers have signed the CLA.

@bradrydzewski
Copy link
Contributor

I think this would be fixed by settings server keepalive:

DRONE_KEEPALIVE_MIN_TIME=20s

and agent keepalive values:

DRONE_KEEPALIVE_TIME=45s
DRONE_KEEPALIVE_TIMEOUT=30s

The deadline exceeded errors typically are a result of a lost network connection, which is typically the result of some sort of network policy (load balancer, etc) that is closing idle connections. This can be prevented with a keepalive.

@hansedong
Copy link
Author

@bradrydzewski Sorry, this setting doesn't work because the network connection is always smooth. The problem I want to fix with this pull request is not caused by the network failure.

@hansedong
Copy link
Author

I have reproduced and fixed this problem in our production environment, and now it works very well, so I would like to ask, can this pull request be merged into the official repository?

@bradrydzewski
Copy link
Contributor

closing since 1.0 no longer uses grpc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants