[SERVER-15283] MapViewOfFileEx for Y:/mongo/slave/mips201409/mips201409.12 failed with error errno:487 (file size is 2146435072) in MemoryMappedFile: Created: 17/Sep/14  Updated: 24/Jan/15  Resolved: 23/Jan/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.4.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: gaoyw Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File log.log    
Operating System: Windows
Participants:

 Description   

OS: Windows Server 2008 R2 ×64 ;machine ram : 128GB
mongoDB :version v2.4.8
dbserver runing more than a month with Master-Slave mode,one node is master,one node is slave.
MapViewOfFileEx for Y:/mongo/slave/db/mips201409/mips201409.12 failed with error errno:487 cannot access(file size is 2146435072) in MemoryMappedFile::createPrivateMap
that cause os restart,and synchronization data from master again



 Comments   
Comment by Matt Kangas [ 18/Sep/14 ]

@gaoyw - is the above result obtained from the server that reported "errno:487 cannot access(file size is 2146435072) in MemoryMappedFile::createPrivateMap"?

I suspect it is not. You said it was your slave that system that failed, please confirm you are obtaining buildInfo from the slave.

You can also examine your log files. Build information is printed to the log when mongod starts.

Comment by gaoyw [ 18/Sep/14 ]

> db.serverBuildInfo();
{
"version" : "2.4.8",
"gitVersion" : "a350fc38922fbda2cec8d5dd842237b904eafc14",
"sysInfo" : "windows sys.getwindowsversion(major=6, minor=1, build=7601,
platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49",
"loaderFlags" : "/nologo /LTCG /DEBUG /LARGEADDRESSAWARE /NODEFAULTLIB:M
SVCPRT",
"compilerFlags" : "/TP /nologo /EHsc /W3 /wd4355 /wd4800 /wd4267 /wd4244
/Z7 /errorReport:none /O2 /Oy- /MT /GL",
"allocator" : "system",
"versionArray" : [
2,
4,
8,
0
],
"javascriptEngine" : "V8",
"bits" : 64,
"debug" : false,
"maxBsonObjectSize" : 16777216,
"ok" : 1
}

bits is 64

Comment by Matt Kangas [ 17/Sep/14 ]

gaoyw - Can you confirm that you are running a 64-bit build of MongoDB, not a 32-bit build?

In the mongo shell please run:

getBuildInfo()

If the "bits" field is 32 then the error you see is expected when the mapped data set size exceeds 2 GB.

FAQ: What are the limitations of 32-bit versions of MongoDB

To fix: download a 64-bit version of MongoDB 2.4.11, install, and restart.

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