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

[EI-370] Timeout if grpc request takes too long #362

Merged
merged 2 commits into from
May 2, 2024
Merged

Conversation

rtso
Copy link
Collaborator

@rtso rtso commented May 1, 2024

Description

When updating grpc image, we observe some processor reconnection hangs when making the grpc request. Example where processor hangs for 2 mins (link).

This adds a 5s timeout to the grpc request. If it takes too long it will retry up to 5 times.

Testing

Restart 3/4 of the data service pods and monitor the processors reconnection

Before

Some processors taking > 1.5 min to reconnect
Screenshot 2024-05-01 at 5 37 23 PM

After

Processors that time out making the grpc request, try to reconnect faster. All processors reconnect faster
Screenshot 2024-05-01 at 5 43 26 PM

@rtso rtso changed the title Timeout if grpc request takes too long [EI-370] Timeout if grpc request takes too long May 2, 2024
Copy link

linear bot commented May 2, 2024

@rtso rtso marked this pull request as ready for review May 2, 2024 00:26
@rtso rtso requested review from a team and grao1991 May 2, 2024 00:45
rust/processor/src/grpc_stream.rs Show resolved Hide resolved
@rtso rtso force-pushed the rtso/reconnection branch from 6c6bd12 to c6ea7ae Compare May 2, 2024 22:02
@rtso rtso merged commit 41461d4 into main May 2, 2024
8 checks passed
@rtso rtso deleted the rtso/reconnection branch May 2, 2024 22:37
yuunlimm pushed a commit that referenced this pull request May 9, 2024
* Timeout if grpc request takes too long

* Add config var
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.

4 participants