[SERVER-4821] Mongos signal 11 (sigsegv) after DBClientCursor::init failure Created: 31/Jan/12 Updated: 25/Jul/14 Resolved: 02/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Johnny Boy | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | mongos | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian Linux with official 10gen mongodb 2.0.2 debs |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
11Setup is 3 shards. One collection was just rebalancing or had just been to the 3rd shard (xxxB2). Mongos crashed on one machine leaving this in the log: Mon Jan 30 16:30:28 [ReplicaSetMonitorWatcher] ReplicaSetMonitor::_checkConnection: mongo1:27027 { setName: "xxxB2", ismaster: false, secondary: true, hosts: [ "mongo1:27027" ], passives: [ "mongo4:27027" ], arbiters: [ "task2:27027" ], me: "mongo1:27027", maxBsonObjectSize: 16777216, ok: 1.0 }Mon Jan 30 16:30:28 [ReplicaSetMonitorWatcher] ReplicaSetMonitor::_checkConnection: mongo4:27027 { setName: "xxxB2", ismaster: false, secondary: true, hosts: [ "mongo1:27027" ], passives: [ "mongo4:27027" ], arbiters: [ "task2:27027" ], passive: true, me: "mongo4:27027", maxBsonObjectSize: 16777216, ok: 1.0 }Mon Jan 30 16:30:30 [conn38697] end connection 172.16.49.111:35486 Mon Jan 30 16:30:40 [ReplicaSetMonitorWatcher] ReplicaSetMonitor::_checkConnection: mongo4:27027 { setName: "xxxB2", ismaster: false, secondary: true, hosts: [ "mongo1:27027" ], passives: [ "mongo4:27027" ], arbiters: [ "task2:27027" ], passive: true, me: "mongo4:27027", maxBsonObjectSize: 16777216, ok: 1.0 }Mon Jan 30 16:30:45 [conn38699] ~ScopedDbConnection: _conn != null |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 02/Feb/12 ] |
|
See |
| Comment by Johnny Boy [ 31/Jan/12 ] |
|
172.16.49.111 is mongo1 |