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

Fail fast for more rediscovery failures #1011

Merged
merged 3 commits into from
Dec 6, 2022

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Oct 26, 2022

When trying to impersonate an invalid user, the routing procedure returns Neo.ClientError.Statement.ArgumentError. This type of failure is not in the fail fast list, thus this is wrapped up in the generic rediscovery error triggering the retry in the transaction functions. Since this kind of error is not recoverable, retrying on it is not need and desirable.

Then, failing fast on Neo.ClientError.Statement.ArgumentError failures speeds up the error bubbling and avoids unnecessary load in the client and server.

Other rediscovery failures to be fast failed are:

  • Neo.ClientError.Statement.TypeError
  • Neo.ClientError.Request.Invalid

@bigmontz bigmontz force-pushed the 5.x-fast-failing-on-wrong-imp branch from 5d90636 to bd5e8d9 Compare November 23, 2022 10:09
@bigmontz
Copy link
Contributor Author

bigmontz commented Nov 23, 2022

@bigmontz bigmontz changed the title Fail fast on rediscovery when 'Neo.ClientError.Statement.ArgumentError' failure Fail fast for more rediscovery failures Nov 24, 2022
@robsdedude robsdedude self-requested a review November 24, 2022 11:16
Copy link

@AndyHeap-NeoTech AndyHeap-NeoTech left a comment

Choose a reason for hiding this comment

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

Straight forward enough. Approved.

Copy link
Member

@robsdedude robsdedude left a comment

Choose a reason for hiding this comment

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

@robsdedude
Copy link
Member

Re-triggered the CI after the TestKit PR has been merged ⏳

…r' failure

When trying to impersonate an invalid user, the routing procedure returns `Neo.ClientError.Statement.ArgumentError`.
This type of failure is not in the fail fast list, thus this is wrapped up in the generic rediscovery error triggering the retry in the transaction functions.
Since this kind of error is not recoverable, retrying on it is not need and desirable.

Then, failing fast on `Neo.ClientError.Statement.ArgumentError` failures speeds up the error bubbling and avoids unnecessary load in the client and server.
@bigmontz bigmontz force-pushed the 5.x-fast-failing-on-wrong-imp branch from 23ee1bf to 1703009 Compare December 6, 2022 12:57
@bigmontz bigmontz merged commit ee72ed0 into neo4j:5.0 Dec 6, 2022
@bigmontz bigmontz deleted the 5.x-fast-failing-on-wrong-imp branch December 6, 2022 15:55
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