[SERVER-5745] profiling shows queries during round about 1271303044 ms (more than 14 days) Created: 02/May/12  Updated: 15/Aug/12  Resolved: 09/May/12

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.0.1, 2.0.2, 2.0.3, 2.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kay Agahd Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Issue Links:
Duplicate
duplicates SERVER-2886 Many commands being executed for 1271... Closed
Operating System: Linux
Participants:

 Description   

After having logged slow queries (>3 sec) I observed a few queries which took about 1271303044 ms (+- 5000 ms).
Could it be that these queries were executed with a noTimeOut option, so they would live "forever" (max ~1271303044 ms) on the mongo server?
Could it be an (unintentional) overflow of some mongo counter which results in termination after around 1271303044 ms?

According to mongo, the longest query took over 14 days (1271309097
ms):
{
"_id" : ObjectId("4f7dc7dc559a38abe85a91cd"),
"ts" : "2012-04-05T14:24:59Z",
"op" : "getmore",
"ns" : "offerStore.offer",
"query" :

{ "missingSince" : null, "shopId" : 5040 }

,
"cursorid" : NumberLong("1817499255547817100"),
"nreturned" : 68132,
"responseLength" : 3883544,
"millis" : 1271309097,
"client" : "#.#.#.#",
"user" : ""

}

Is this reliable?

The system time of mongod and mongos did not change that much. They are synced by ntp.

Related forum threads:
http://groups.google.com/group/mongodb-user/browse_thread/thread/6323765b69e79208
http://groups.google.com/group/mongodb-user/browse_thread/thread/7378a4610f1c9bf2



 Comments   
Comment by Randolph Tan [ 09/May/12 ]

Hi Agahd, please check SERVER-2886 for updated findings on this bug.

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