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

Trigger rediscovery when failing to send a message on a streaming call #222

Merged
merged 1 commit into from
Sep 15, 2022

Conversation

timothycoleman
Copy link
Contributor

@timothycoleman timothycoleman commented Sep 9, 2022

  • Duplex streaming and client streaming.

Before this, persistent subscriptions could keep retrying subscribing to a down node without rediscovering. This could happen if the original subscription failed while sending an ack (we were not triggering a rediscovery on failed send) and then on retry we send the ReadReq (which would fail, not triggering rediscovery) before trying to read from the server.

- Duplex streaming and client streaming.

Before this, persistent subscriptions could keep retrying subscribing to a down node without rediscovering.
This could happen if the original subscription failed while sending an ack (we were not triggering a rediscovery on failed send)
and then on retry we send the ReadReq (which would fail, not triggering rediscovery) before trying to read from the server.
@timothycoleman timothycoleman merged commit adb2ef7 into master Sep 15, 2022
@timothycoleman timothycoleman deleted the trigger-rediscovery-on-send-fail branch September 15, 2022 14:24
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