[SERVER-389] map/reduce kaboom Created: 27/Oct/09  Updated: 12/Jul/16  Resolved: 29/Nov/09

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

Type: Bug Priority: Critical - P2
Reporter: Dwight Merriman Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

is this a memory leak? Additionally, should the MR abort on a userexception???

> m = function()

{ if(this.prop1=='men') emit(this.uid); }

function () {
if (this.prop1 == "men")

{ emit(this.uid); }

}
> r = function(k,values)

{ return values[0]; }

function (k, values) {
return values[0];
}
> db.small.mapReduce(m,r);

many of these:
Tue Oct 27 12:42:52 User Exception _id cannot be an array
Tue Oct 27 12:42:52 logs.tmp.mr.small_1256661405_1 Caught Assertion update, continuing
Tue Oct 27 12:42:52 User Exception _id cannot be an array
Tue Oct 27 12:42:52 logs.tmp.mr.small_1256661405_1 Caught Assertion update, continuing
Tue Oct 27 12:42:53 User Exception _id cannot be an array
Tue Oct 27 12:42:53 logs.tmp.mr.small_1256661405_1 Caught Assertion update, continuing
Tue Oct 27 12:42:55 logs.tmp.mr.small_1256661405_1 Caught Assertion update, continuing
Tue Oct 27 12:42:55 User Exception _id cannot be an array
Tue Oct 27 12:42:55 logs.tmp.mr.small_1256661405_1 Caught Assertion update, continuing
then:
12390900/35961649 34%

#

  1. Fatal error in CALL_AND_RETRY_2
  2. Allocation failed - process out of memory
    #

Tue Oct 27 12:42:59 Got signal: 6 (Aborted).
Tue Oct 27 12:42:59 Backtrace:
0x5893d9 0x2aaaac125f30 0x2aaaac125ec5 0x2aaaac127970 0x62d2e9 0x5bd20d 0x5cf38c 0x5d207a 0x5ac43f 0x5ac474 0x493443 0x485c94 0x57b48a 0x505e0e 0x498911 0x49b549 0x53235a 0x5351de 0x58a0a5 0x2aaaab1e9d8e
./mongod(_ZN5mongo10abruptQuitEi+0x399) [0x5893d9]
/lib64/libc.so.6 [0x2aaaac125f30]
/lib64/libc.so.6(gsignal+0x35) [0x2aaaac125ec5]
/lib64/libc.so.6(abort+0x110) [0x2aaaac127970]
./mongod [0x62d2e9]
./mongod [0x5bd20d]
./mongod [0x5cf38c]
./mongod [0x5d207a]
./mongod [0x5ac43f]
./mongod [0x5ac474]
./mongod [0x493443]
./mongod [0x485c94]
./mongod [0x57b48a]
./mongod [0x505e0e]
./mongod [0x498911]
./mongod [0x49b549]
./mongod [0x53235a]
./mongod [0x5351de]
./mongod(_ZN5mongo10connThreadEv+0x205) [0x58a0a5]
/usr/lib64/libboost_thread-mt.so.3(_ZNK5boost9function0IvSaINS_13function_baseEEEclEv+0xbe) [0x2aaaab1e9d8e]
Tue Oct 27 12:42:59 dbexit:



 Comments   
Comment by Eliot Horowitz (Inactive) [ 29/Nov/09 ]

i believe both issues were fixed with M/R re-architecture

Generated at Thu Feb 08 02:53:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.