[SERVER-5377] Empty rows for mapreduce -> lock all db Created: 23/Mar/12  Updated: 08/Mar/13  Resolved: 17/Jan/13

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

Type: Bug Priority: Critical - P2
Reporter: Azat Khuzhin Assignee: Stennie Steneker (Inactive)
Resolution: Incomplete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 GNU/Linux


Operating System: Linux
Participants:

 Description   

Instead of
%database - real db name
%collection - real collection name (~ 26 millions of rows)

> db.currentOp().inprog.forEach(function(row) { if (row.active) print(tojson(row)); } );
{
        "opid" : 16617560,
        "active" : true,
        "lockType" : "read",
        "waitingForLock" : false,
        "secs_running" : 7941,
        "op" : "query",
        "ns" : "%database.%collection",
        "query" : {
                "$msg" : "query not recording (too large)"
        },
        "client" : "127.0.0.1:45898",
        "desc" : "conn",
        "threadId" : "0x7f8aa72f2700",
        "connectionId" : 84024,
        "msg" : "m/r: (1/3) emit phase",
        "numYields" : 19082
}
 
$ ps aux | grep mongod
mongodb   5400  6.2 44.1 151646464 14563872 ?  Sl   Mar20 197:08 /usr/bin/mongod --dbpath /work1/mongodb --logpath /var/log/mongodb-local/mongodb-local.log --config /etc/mongodb-local.conf run
 
> getMemInfo()
{ "virtual" : 113, "resident" : 76 }
 
> db.stats()
# .......... wait to long, and nothing
 
> db.currentOp().inprog.length
19998
 
$ tail /var/log/mongodb-local/mongodb-local.log                                                                   
Thu Mar 22 13:22:50 [initandlisten] connection accepted from 127.0.0.1:51562 #633178                                                    
Thu Mar 22 13:22:50 [initandlisten] connection refused because too many open connections: 20000                                         
Thu Mar 22 13:22:50 [initandlisten] connection accepted from 127.0.0.1:51563 #633179                                                    
Thu Mar 22 13:22:50 [initandlisten] connection refused because too many open connections: 20000                                         
Thu Mar 22 13:22:50 [initandlisten] connection accepted from 127.0.0.1:51564 #633180                                                    
Thu Mar 22 13:22:50 [initandlisten] connection refused because too many open connections: 20000                                         
Thu Mar 22 13:22:50 [initandlisten] connection accepted from 127.0.0.1:51565 #633181                                                    
Thu Mar 22 13:22:50 [initandlisten] connection refused because too many open connections: 20000                                         
Thu Mar 22 13:22:50 [initandlisten] connection accepted from 127.0.0.1:51566 #633182            

And now I kill this MR job

> db.killOp(16617560)
{ "info" : "attempting to kill op" }
> db.currentOp().inprog.length
19502
> db.currentOp().inprog.length
17396



 Comments   
Comment by Stennie Steneker (Inactive) [ 17/Jan/13 ]

Hi Azat,

Thanks for the update .. closing the issue.

Cheers,
Stephen

Comment by Azat Khuzhin [ 17/Jan/13 ]

Hi Stephen,

I did a little test right now, on collection with 1 document, and can't reproduce this bug with 2.2.2-rc1
But I couldn't check this now on full database, because I need to copy database snapshot first.

So I think you can close it, if I can reproduce this in future, than I'll comment this issue.

Thanks.

Comment by Stennie Steneker (Inactive) [ 17/Jan/13 ]

Hi Azat,

Just checking if you have any update .. is this still an issue since you upgraded to MongoDB 2.2?

Thanks,
Stephen

Comment by Azat Khuzhin [ 11/Dec/12 ]

Hi Stephen,

Yes, I upgrade mongodb up to 2.2.
I'll try to do it in a week.

Thanks.

Comment by Stennie Steneker (Inactive) [ 10/Dec/12 ]

Hi Azat,

This issue was opened some time ago against MongoDB 2.0.3.

Have you upgraded to a newer version of MongoDB, and are you still encountering this problem?

Can you provide a sample of your document structure and Map/Reduce code so we can try to reproduce the issue?

Thanks,
Stephen

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