Skip to content

Improve failure handling for RESET and ACK_FAILURE #376

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

Merged
merged 2 commits into from
May 30, 2018

Conversation

lutovich
Copy link
Contributor

Removed RESET that does not mute ACK_FAILURE handling.

Both RESET and ACK_FAILURE messages will now be immediately flushed to the network to make sure connections are fully cleaned up before being returned to the pool. Outbound messages will only be sent if the connection is not broken. Failure to RESET or ACK_FAILURE will be considered a fatal error, unless ACK_FAILURE was ignored because of a subsequent RESET.

Removed RESET that does not mute ACK_FAILURE handling.
@lutovich lutovich requested a review from ali-ince May 24, 2018 18:01
Both RESET and ACK_FAILURE messages will now be immediately flushed to
the network to make sure connections are fully cleaned up before being
returned to the pool. Outbound messages will only be sent if the
connection is not broken. Failure to RESET or ACK_FAILURE will be
considered a fatal error, unless ACK_FAILURE was ignored because of
a subsequent RESET.
@lutovich lutovich force-pushed the 1.7-ack_failure-and-reset-failures branch from f324878 to 6a49a99 Compare May 24, 2018 22:42
@ali-ince ali-ince merged commit 2c2ae55 into neo4j:1.7 May 30, 2018
@lutovich lutovich deleted the 1.7-ack_failure-and-reset-failures branch May 30, 2018 12:08
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