-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
Currently there is no way to wait for background threads to terminate. This most notably creates races in SDAM tests which manually run inspectors on the topology while said background threads could also possibly be running the inspectors.
On a related note, the stop? call returns true if the thread is killed or suspended, and should be replaced with alive? calls to indicate whether a thread is killed.
- related to
-
RUBY-1357 Client constructor does I/O contrary to spec requirements
- Closed