-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
It seems that the cluster's finalizer, specifically the part that ends sessions, may be invoked after the server's connection pools have been closed. In this case the cluster's finalizer will create new connections, which 1) is wasteful since it could've used already existing connections and 2) the new connections may not be properly torn down as the pool's finalizer may have already executed.
- duplicates
-
RUBY-1868 Reduce non-determinism in the whole of ruby test suite
- Closed