Turn backoff off for routed connections

Author: madchicken

lib/src/pool.rs

@@ -31,7 +31,7 @@ impl ConnectionManager {
     }
 
     pub fn backoff(&self) -> Option<ExponentialBuilder> {
-        self.backoff.clone()
+        self.backoff
     }
 }
 

lib/src/routing/connection_registry.rs

@@ -176,6 +176,7 @@ async fn refresh_routing_table(
             server.clone(),
             create_pool(&Config {
                 uri,
+                backoff: None,
                 ..config.clone()
             })?,
         );

lib/src/routing/routed_connection_manager.rs

@@ -1,4 +1,3 @@
-use crate::config::BackoffConfig;
 use crate::pool::ManagedConnection;
 use crate::routing::connection_registry::{
     start_background_updater, BoltServer, ConnectionRegistry, RegistryCommand,
@@ -28,6 +27,9 @@ const ROUTING_TABLE_MAX_WAIT_TIME_MS: i32 = 5000;
 
 impl RoutedConnectionManager {
     pub fn new(config: &Config, provider: Arc<dyn RoutingTableProvider>) -> Result<Self, Error> {
+        // backoff config should be set to None here, since the routing table updater will handle retries
+        // We could provide some configuration to "force" the retry mechanism in a clustered env,
+        // but for now we will turn it off
         let backoff = config
             .backoff
             .clone()