[SERVER-11294] Assertion: 16105 stack trace in dbstats command Created: 21/Oct/13 Updated: 11/Jul/16 Resolved: 25/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
I unfortunately don't have a quick reproducible test case for kernel team use. Fortunately, it is relatively easily reproducible by members of the MMS team(1). I believe the MMS Monitoring agent is issuing the offending query/command to a standalone MongoD. I'm sure any context from the kernel team from the stack trace will help narrow down the details necessary to create a small reproducible test case. I'm also not positive that there's any actual degraded/undefined behavior that accompanies the stack trace. (1) (Hard way) to reproduce:
Unfortunately, the mms agent does not seem to notice a problem and seemingly operates normally. |
| Comments |
| Comment by Daniel Gottlieb (Inactive) [ 25/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Looks good! | |||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 25/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Should be fixed, please try again. | |||||||||||||||||||||||||||||||
| Comment by auto [ 25/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: | |||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 24/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Have a fix locally, behind one other thing | |||||||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 23/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Reran tests on the current master HEAD: `2b16aca77cbd4486d780e21636b7043733e12765`. I aborted the full test plan due to receiving seemingly different errors at the end of the mms server coming up (thus not caused by the monitoring agent). Stacktrace:
Full logs with -vv is being attached. | |||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 21/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Cool, thanks Dan. We can try with the new code later too but the log level is more informative now, as you can see. Also, all local dbstats show the same stack trace in the log file.
| |||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 21/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Dan, log level and profile level are two different things: Command line flag for log level (-v*): http://docs.mongodb.org/manual/reference/program/mongod/#cmdoption--verbose DB Profiling (system.profile collection): http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/#db.setProfilingLevel | |||||||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 21/Oct/13 ] | |||||||||||||||||||||||||||||||
|
What Cailin said. Running with profiling set to 2... Edit: The agent is not showing signs of receiving an error. | |||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 21/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Do you know if there is an error returned to the agent? Also, if you can provide logs at level 2 that would be helpful, or more logs around that event. A quick test of running dbstats across new databases and the local db 1000 times in a loop did not turn up the message for me. | |||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 21/Oct/13 ] | |||||||||||||||||||||||||||||||
|
Looks like this line DBStats::run():
|