[SERVER-2948] Cannot create large index with journaling enabled (errno:1450) windows Created: 14/Apr/11  Updated: 29/May/12  Resolved: 02/Sep/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 1.8.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Conor McCarthy Assignee: Dwight Merriman
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

64bit mongodb sever
Windows 2003 x64 SP2
Dell PowerEdge 2900 III.
24GB RAM
15k SAS drive
2.4Ghz quad core


Operating System: Windows
Participants:

 Description   

Database server crashed when creating an reasonably large index with --journal startup flag. This is repeatable. The index is created successfully when --journal is not enabled.
Log:

149682900/150461788 99%
149933600/150461788 99%
Thu Apr 14 00:05:18 [DataFileSync] flushing mmap took 360ms for 269 files
150228400/150461788 99%
Thu Apr 14 00:05:31 [conn3] done building bottom layer, going to commit
Thu Apr 14 00:05:32 [conn3] warning exception in dur::journal error appending to file errno:1450 Insufficient system resources exist to complete the requested service.
Thu Apr 14 00:05:32 [conn3] dbexception in groupCommit causing immediate shutdown: 13517 error appending to file errno:1450 Insufficient system resources exist to complete the requested service.
Thu Apr 14 00:06:18 [DataFileSync] flushing mmap took 282ms for 269 files



 Comments   
Comment by Eliot Horowitz (Inactive) [ 02/Sep/11 ]

Likely fixed in 1.8.3

Comment by Dwight Merriman [ 03/May/11 ]

i have committed something that might fix it, and will log more information regardless. can you give it a try when it's up in a daily build?

Comment by auto [ 03/May/11 ]

Author:

{u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}

Message: try to fix SERVER-2948 journaling windows error message
Branch: master
https://github.com/mongodb/mongo/commit/8b0e7ecde68404c527f54ca14c4aed2fac2ae916

Comment by Mathias Stearn [ 03/May/11 ]

I think the issue is that we are trying to write too much data in a single WriteFile call.

Generated at Thu Feb 08 03:01:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.