-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Spec Comp
-
None
> The client's constructor MUST NOT do any I/O.
However the following will hang for a while, note the timeout message:
averagest% irb -Ilib -rmongo irb(main):001:0> m=Mongo::Client.new(['12.12.12.12']) D, [2018-06-12T19:28:54.498585 #15714] DEBUG -- : MONGODB | EVENT: #<Mongo::Monitoring::Event::TopologyOpening topology=Unknown> D, [2018-06-12T19:28:54.498822 #15714] DEBUG -- : MONGODB | Topology type 'unknown' initializing. D, [2018-06-12T19:28:54.499146 #15714] DEBUG -- : MONGODB | EVENT: #<Mongo::Monitoring::Event::ServerOpening address=12.12.12.12:27017 topology=Unknown> D, [2018-06-12T19:28:54.499280 #15714] DEBUG -- : MONGODB | Server 12.12.12.12:27017 initializing. m D, [2018-06-12T19:29:04.502460 #15714] DEBUG -- : MONGODB | execution expired => #<Mongo::Client:0x47151180222960 cluster=12.12.12.12:27017> irb(main):002:0> m
- is related to
-
RUBY-1462 Remove single round of sdam in Client constructor
- Backlog
-
RUBY-1520 Optionally wait for background threads to terminate
- Closed
-
RUBY-1547 Inline cluster rescans must be concurrent/done by monitor
- Closed
-
RUBY-1549 Correctly handle monitoring thread death in constructor sdam wait
- Closed
-
RUBY-1582 Use server description's last update time when waiting for first sdam round
- Closed
- related to
-
RUBY-1434 Document low server selection timeout in development mode
- Closed