mongodb hangs in production with 2.0, needs a pkill and restart

[Patrick Aljord]

Hi all,

I've just upgraded to mongodb 2.0 from 1.8 and every hour or so,
mongodb completely hangs (any query or just "show tables" won't work)
and the only way to get it back is by killing the process and
restarting manually. The app used to work fine before.

This is what db.currentOp() returns before I kill it:
http://pastebin.com/gs1tN09U

I didn't have mongostat running when it went off but this is what I
have right now and usually: http://pastebin.com/tGpwtJEG

Any idea what's wrong? Could it be the durability hanging the db? It
was off with 1.8...

Thanks in advance,

Pat

[Mathias Stearn]

I think this op is your problem:

{
"opid" : 802235,
"active" : true,
"lockType" : "write",
"waitingForLock" : false,
"secs_running" : 804,
"op" : "query",
"ns" : "shapado-production",
"query" : {
"$msg" : "query not recording (too large)"
},
"client" : "127.0.0.1:54079",
"desc" : "conn",
"threadId" : "0x7f894028d700",
"connectionId" : 1323,
"numYields" : 0
},

Unfortunately it's not clear what that is doing but if I had to guess I'd say it was either a findAndModify or a db.eval. The latter seems more likily since it was running for 804 seconds. Are you using that anywhere?