[SERVER-2901] mongod becomes unreachable on 32-bit Amazon EC2 instances Created: 05/Apr/11 Updated: 05/Apr/11 Resolved: 05/Apr/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | Remon van Vliet | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 32-bit Deb EC2 |
||
| Participants: |
| Description |
|
mongod process starts complaining about it's inability to create new threads. This while there's only 6mb worth of data in the database and there's no resource on the machine even close to being exhausted it looks like. Happens consistently around 310-330 connections. Curious if you can point me in the right direction on this. mongod log : http://pastie.org/1758994 |
| Comments |
| Comment by Remon van Vliet [ 05/Apr/11 ] |
|
We see connection bursts coming from our app servers occasionally that look like the cause. Bit odd with maxConnections on 100 so may be Guice issue with injecting Mongo instances as singletons. Close this for now. |
| Comment by Remon van Vliet [ 05/Apr/11 ] |
|
Actually, I'm still confused. We don't actually have 300 connections open, it's about 30. |
| Comment by Remon van Vliet [ 05/Apr/11 ] |
|
Close this, found Eliot's reply about 8mb per connection used. |