[SERVER-16268] 2.8 Dumps stacktrace when stopped with Control^C Created: 21/Nov/14 Updated: 10/Dec/14 Resolved: 21/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.8.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | John Page | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | Start 2.8 hit with a heavy update / write load |
| Participants: |
| Description |
|
mongod(_ZN5mongo15printStackTraceERSo+0x29) [0xf6ffb9] |
| Comments |
| Comment by Eric Milkie [ 21/Nov/14 ] |
|
It was actually possible to get a stack trace in 2.6 as well, depending on your workload. For developer and training scenarios, are users commonly shutting down servers that are under heavy load? |
| Comment by John Page [ 21/Nov/14 ] |
|
It means we will have a lot of customers see stack traces - this didn't happen in 2.6 so it may well work as designed but it looks broken. |
| Comment by Eric Milkie [ 21/Nov/14 ] |
|
Thanks. |
| Comment by John Page [ 21/Nov/14 ] |
|
Attached Log copied and pasted from terminal window. wasnt being logged to a file, sorry. |
| Comment by Eric Milkie [ 21/Nov/14 ] |
|
Can you attach the full log? |