[SERVER-17922] Insert fails capped collection which is completely filled Created: 08/Apr/15 Updated: 10/Apr/15 Resolved: 10/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Arati Sethy | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, MongoDB shell version: 2.2.2 , I could see below logs from mongod server for sometime. Wed Mar 11 04:18:24 [conn1] insert: couldn't alloc space for object ns:log.log capped:1 Please guide how to debug and resolve this issue. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 10/Apr/15 ] |
|
Hello, According to our support policy, 2.2 has reached end-of-life. You can see our support policy although I understand the complication in upgrading for your case, we are not able to continue to maintain and update 2.2. You can always reach out to the google group for help on issues with upgrading or issues with older versions and special situations. I'm going to close this ticket for now, but we'd be happy to look into this issue again if we can reproduce it on a current version of MongoDB. Regards, |
| Comment by Arati Sethy [ 09/Apr/15 ] |
|
Hi Sam, drwxr-xr-x 2 root root 4.0K Apr 9 08:15 journal/ My Application is running on a 4GB RAM box with 450GB hard disk out of which 330G is still free. I have neither restarted mongod server nor dropped and created the collection again. I have same application running on 100 such server, this issue is seen only on one server. So I guess, there is no straing forward condition to reproduce this issue. Thanks, |
| Comment by Sam Kleinman (Inactive) [ 08/Apr/15 ] |
|
The shell example that you posted uses version 2.2 of the shell. Is the mongod that you're using also 2.2? If you are using 2.2, is there anything that's preventing you from upgrading to a more recent version of MongoDB? Once we can ensure that we're running one of the currently supported versions of MongoDB (at least 2.6 and preferably 3.0), it would be good to understand:
For upgrade information see the following documents: You can also contact one of our support channels for more help with upgrade-related issues. I hope this helps and that we can help discover the underlying cause of the behavior that you're seeing as quickly as possible. Cheers, |