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

[FIXED] RAFT Transport timeouts #988

Merged
merged 1 commit into from
Dec 11, 2019
Merged

Conversation

kozlovic
Copy link
Member

Keep a 2sec for the dial and flush, but increase the timeout for
read operations. This will reduce the risk of getting these
type of errors:

[ERR] STREAM: raft-net: Failed to flush response: write to closed conn

Signed-off-by: Ivan Kozlovic ivan@synadia.com

Keep a 2sec for the dial and flush, but increase the timeout for
read operations. This will reduce the risk of getting these
type of errors:

```
[ERR] STREAM: raft-net: Failed to flush response: write to closed conn
```

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 92.064% when pulling b4b3716 on cluster_raft_tport_timeout into e1ae749 on master.

Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kozlovic kozlovic merged commit dbd20ed into master Dec 11, 2019
@kozlovic kozlovic deleted the cluster_raft_tport_timeout branch December 11, 2019 21:13
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.

3 participants