Fixed Bug:- Multi-Driver Failover when one of multiple hosts down #282
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Multi-Driver Failover When Primary Node Is Down
Failover Handling Implementation
Added support for failover when the highest-priority Neo4j driver is unavailable.
DriverSetupManager now continues to next available driver instead of failing immediately.
Exception Handling Improvements
Neo4jConnectionPool::acquire() now throws ConnectionPoolException instead of RuntimeException.
Neo4jDriver::verifyConnectivity() catches both ConnectException and RuntimeException.
Defensive try-catch added in DriverSetupManager::getDriver() to log and skip failed drivers.
Routing & Connectivity
Client properly attempts secondary drivers when primary fails.
Connection pool and driver retry logic updated to ensure uninterrupted operations.
Testing & Compliance
Unit tests added in MultiDriverFailoverTest and ClientExceptionHandlingTest.
Tests verify driver fallback, client-level transactions, and complete failover flow.