-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: legacy-0.0-26compat-2.6.0-rc0
-
Component/s: None
-
Environment:3.11.0-17-generic #31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
g++ 4.8.1
mongo 2.5.5 + shared client driver
With a simple snippet like this
mongo::ScopedDbConnection a("myset/127.0.0.1:27017");
a.done();
I get repeating warnings in console (of my application) :
2014-02-22T14:22:53.843+0200 [ReplicaSetMonitorWatcher] scoped connection to 127.0.0.1:27017 not being returned to the pool
2014-02-22T14:22:53.843+0200 [ReplicaSetMonitorWatcher] scoped connection to 127.0.0.1:27019 not being returned to the pool
I initially thought it is because my replicaset contains one replica (only primary), but after adding another to the se, I saw the same, except now for both replicas.
What makes this more strange is that the same test with the connection string: "127.0.0.1:27017" (no myset) does not have any warnings.