[SERVER-7678] tests failing with too little address space on 32-bit machines Created: 15/Nov/12  Updated: 02/Aug/18  Resolved: 30/Dec/12

Status: Closed
Project: Core Server
Component/s: Build, MapReduce
Affects Version/s: None
Fix Version/s: 2.3.2

Type: Task Priority: Critical - P2
Reporter: Ian Whalen (Inactive) Assignee: Gregory McKeon (Inactive)
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File zbigMapReduce.txt    
Issue Links:
Related
is related to SERVER-7685 nestedarr1.js failing os x 64-bit debug Closed
Participants:

 Description   

zbigMapReduce.js - http://buildlogs.mongodb.org/Linux%20RHEL%2032-bit/builds/1046/test/recent%20failures/zbigMapReduce.js
mrShardedOutput.js - http://buildlogs.mongodb.org/Linux%2032-bit/builds/5284/test/recent%20failures/mrShardedOutput.js



 Comments   
Comment by auto [ 16/Dec/12 ]

Author:

{u'date': u'2012-12-16T23:53:00Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}

Message: SERVER-7678 Display MapReduce results before assertion

Move display of MapReduce results to before the assert test to help debugging.
Branch: master
https://github.com/mongodb/mongo/commit/2dbcc5f6119adbabe2b972c5113546aa36fab137

Comment by auto [ 07/Dec/12 ]

Author:

{u'date': u'2012-12-04T18:26:23Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}

Message: SERVER-7678 Reduce document count in mrShardedOutput.js for 32-bit

Reduce the number of documents inserted per iteration from 100,000
to 30,000 in jstests/sharding/mrShardedOutput.js when run on a 32-bit
system. Do not print the list of inserted documents when the count
is wrong, just display the documents that are missing. Add logging
so we can see where we are in the test if something goes wrong.
Branch: master
https://github.com/mongodb/mongo/commit/034512991dd4f8beb0bdccef33c18ff05cf4e27e

Comment by Ian Whalen (Inactive) [ 03/Dec/12 ]

appears to be failing intermittently on RHEL 32-bit: http://buildlogs.mongodb.org/Linux%20RHEL%2032-bit/builds/1115/test/sharding/mrShardedOutput.js

Comment by Daniel Pasette (Inactive) [ 21/Nov/12 ]

Message: buildbot zbigMapReduce.js make sure we're more fully under memory limit on 32-bit systems
Branch: master
https://github.com/mongodb/mongo/commit/52022a72aa802118357f2aa78d482d8b93a0d9aa

Comment by Tad Marshall [ 18/Nov/12 ]

This also fails on Linux 32-bit. We're running out of virtual address space:
http://buildlogs.mongodb.org/Linux%2032-bit/builds/5279/test/recent%20failures/zbigMapReduce.js

Sun Nov 18 13:49:11.383 exec error: src/mongo/shell/collection.js:931 map reduce failed:{
	"ok" : 0,
	"errmsg" : "MR parallel processing failed: { errmsg: \"exception: can't map file memory - mongo requires 64 bit build for larger datasets\", code: 10084, ok: 0.0 }"
}
throw "map reduce failed:" + tojson(raw);
                           ^
failed to load: /mnt/slaves/Linux_32bit/mongo/jstests/sharding/zbigMapReduce.js

RHEL 32-bit doesn't give such a clear indication, though it is likely the same problem. It shows other issues:

 m29000| Sat Nov 17 10:01:32.537 [PeriodicTask::Runner] task: DBConnectionPool-cleaner took: 29ms
 m29000| Sat Nov 17 10:26:29.913 [DataFileSync] flushing mmaps took 1514373ms  for 3 files

It's true: 1514.373 seconds to flush 3 files really is 25 minutes, as shown in the timestamps.

We may need to pare this test down to make it pass in 32-bit.

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