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

Handle nsqd disconnects #16

Merged
merged 1 commit into from
Mar 7, 2024
Merged

Conversation

Americas
Copy link
Collaborator

This PR essentially does 2 things :

  • Updates the lookup errors event from error to error lookup, this makes it so that lookup failures don't have to be handled, and don't interfere with actual reader errors.
  • Updates the reconnection mixin to emit a disconnect event if the max reconnection attempts for a connection is reached. This is used in the reader to remove these connections from the set of active connections.

@Americas Americas self-assigned this Feb 23, 2024
@Americas Americas force-pushed the support/handle-disconnections branch from b0b6b3a to 58964b4 Compare March 5, 2024 11:20
Copy link

@jspranger jspranger left a comment

Choose a reason for hiding this comment

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

Code-wise, looks fine.

I have tested in the reliability cluster with the backend project and multiple nsqlookupd instances.
I've scaled down all nsqlookupd instances and executed a transaction, which remained processing.
Once I scaled back up an instance of nsqlookupd the transaction completed.

Handlers that didn't have this commit in them, crashed once the nsqlookupd was scaled down. No disruptions were observed to the handlers that had this commit.

LGTM.

@Americas Americas merged commit 348ea73 into master Mar 7, 2024
1 check passed
@Americas Americas deleted the support/handle-disconnections branch March 7, 2024 14: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.

2 participants