-
Notifications
You must be signed in to change notification settings - Fork 73
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
1. Add support for routing table specific TestKit messaged (retrieving routing tables and forcing updates) 2. Improve logging in the TestKit backend (all logs-driver and bolt-got both to stdout and TestKit) for easier debugging 3. Overhaul how/when the driver drops servers from the cached routing table: * Move logic of deactivating servers on failures into the pool. This functionality should not only be present when using transaction functions. * Drop writers on certain error codes: `Neo.ClientError.Cluster.NotALeader` and `Neo.ClientError.General.ForbiddenOnReadOnlyDatabase` 4. To simplify the code and avoid deadlocks or inconsistent driver states, both pool and router use blocking locks now. However, they will never perform IO while holding the lock removing the need for lock acquisition timeouts. * Reformat feature list to reflect TestKit's state * Clean up test skips * TestKit backend: improve logging Log everything to stdout + TestKit socket. * Drop servers from routing table on IO failure * Remove writer from routing table on certain errors * Refactor responsibilities and locking The retry state is no longer responsible for invalidating servers on broken connections. The pool and/or routing logic should take care of that. This is necessary and logical since invalidation should happen regardless of which API (session.Run, transaction.Run, ...) is used. Pool and router no longer do any IO while holding locks. Hence, the locks can be turned into blocking locks without risking blocking for too long. * Add support for RT related TestKit messages * Remove unused context parameters --------- Signed-off-by: Rouven Bauer <rouven.bauer@neo4j.com> Co-authored-by: Florent Biville <florent.biville@neo4j.com>
- Loading branch information
1 parent
ee7546f
commit 39d4411
Showing
39 changed files
with
943 additions
and
719 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.