[SERVER-2682] Absurd query times printed in log Created: 04/Mar/11 Updated: 12/Jul/16 Resolved: 06/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Roy Smith | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux dev1.songza.com 2.6.32-305-ec2 #9-Ubuntu SMP Thu Apr 15 08:05:38 UTC 2010 x86_64 GNU/Linux |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
We're running "1.6.5-pre-". We've got a few lines in our mongodb log which look like the following. Note the absurd elapsed time. mongodb: Fri Mar 4 15:23:20 [conn223] query song_info.songs ntoreturn:1 reslen:324 nscanned:1 { song_id: 459242 }nreturned:1 1271310312ms It doesn't happen very often. In the log file I happened to look at, we've got about 4000 slow queries, of which 4 exhibit this odd behavior. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 06/Mar/11 ] |
|
This was fixed in 1.7, can't remember exactly where right now, but will be in 1.8 |