-
Notifications
You must be signed in to change notification settings - Fork 134
Open
Milestone
Description
With Neo4j v2's new error classifications, we now know which errors are transient and will likely go away with a simple retry:
http://neo4j.com/docs/stable/status-codes.html
We could/should implement (configurable) auto-retry for queries that hit transient errors.
https://groups.google.com/d/topic/neo4j-ecosystem/1apg9CK34e4/discussion
Aspects to consider/implement:
- Option to configure how many times to auto-retry, if any. Default to 2?
- Callback when a retry is happening, so the app can e.g. log a warning if it likes?
- Any delay or backoff between retries? Exponential backoff feels like overkill for only a couple of retries, but might still be wise?