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.

Sign up for GitHub

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

Jump to bottom

Client-side network failures should be self-healing when client-side network connection restored #1954

Open
tjtelan opened this issue Nov 30, 2021 · 1 comment
Open

Client-side network failures should be self-healing when client-side network connection restored #1954

tjtelan opened this issue Nov 30, 2021 · 1 comment
Labels
no-stale Opt-out of closing issue due to no activity

Comments

@tjtelan
Copy link
Contributor

tjtelan commented Nov 30, 2021

Related to #1514

This should be captured in a test. The expectation is if we open a consumer stream, and then simulate a network failure (like if we use iptables to block all outgoing traffic), the client should not disconnect or error out during the network outage.

When outgoing traffic is restored, the expected behavior is the client should resume receiving data from the stream w/o user interaction.
@tjtelan tjtelan changed the title Client-side network failures should be self-healing when network connection restored Client-side network failures should be self-healing when client-side network connection restored Nov 30, 2021
@tjtelan tjtelan mentioned this issue Nov 30, 2021
Open
@github-actions
Copy link

Stale issue message

@morenol morenol added no-stale Opt-out of closing issue due to no activity and removed no-issue-activity labels Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
no-stale Opt-out of closing issue due to no activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tjtelan @morenol