Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.2.0
-
None
-
ALL
Description
When mongodump is run against a replica set string :
./mongodump --host foo/host1,host2 it throws a segmentation fault. See below :
sid@ferrari:~/10gen/mongo$ ./mongodump --host foo/ferrari:31000,ferrari:31001
|
Mon Sep 10 13:11:12 starting new replica set monitor for replica set foo with seed of ferrari:31000,ferrari:31001
|
Mon Sep 10 13:11:12 successfully connected to seed ferrari:31000 for replica set foo
|
Mon Sep 10 13:11:12 changing hosts to { 0: "ferrari:31000", 1: "ferrari:31001" } from foo/
|
Mon Sep 10 13:11:12 trying to add new host ferrari:31000 to replica set foo
|
Mon Sep 10 13:11:12 successfully connected to new host ferrari:31000 in replica set foo
|
Mon Sep 10 13:11:12 trying to add new host ferrari:31001 to replica set foo
|
Mon Sep 10 13:11:12 successfully connected to new host ferrari:31001 in replica set foo
|
Mon Sep 10 13:11:12 Primary for replica set foo changed to ferrari:31000
|
Mon Sep 10 13:11:12 replica set monitor for replica set foo started, address is foo/ferrari:31000,ferrari:31001
|
Mon Sep 10 13:11:12 [ReplicaSetMonitorWatcher] starting
|
connected to: foo/ferrari:31000,ferrari:31001
|
Mon Sep 10 13:11:12 all dbs
|
Logstream::get called in uninitialized state
|
Mon Sep 10 13:11:12 deleting replica set monitor for: foo/ferrari:31000,ferrari:31001
|
Segmentation fault
|
Attachments
Issue Links
- depends on
-
SERVER-7801 Potential access to freed memory by Tool::conn()
-
- Closed
-
- duplicates
-
SERVER-7006 mongo tools seg fault in 2.2.0 with replica sets in connection string
-
- Closed
-
- is related to
-
SERVER-7612 explicit primary read pref does not work well with shard versioning
-
- Closed
-