[SERVER-16627] Stack trace when fail to open WiredTigerSession Created: 22/Dec/14 Updated: 16/Apr/15 Resolved: 16/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.8.0-rc3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Robert Guo (Inactive) |
| 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: | To reproduce the error, start a mongod with wiredTiger, insert some documents using the shell, turn on the fail point in WiredTigerSession::WiredTigerSession, this should cause the server to crash. The stack trace of the crash is attached in a text file More detailed steps: Add a fail point:
Invoke it from the shell:
|
||||||||||||||
| Participants: |
| Description |
|
A failed call to a WT_CONNECTION's open_session after mongod has started causes it to crash. The wiredTiger open_session failure error condition is simulated by setting the conn->open_session call's return code in WiredTigerSession::WiredTigerSession to ENOENT using a fail point. |
| Comments |
| Comment by Eitan Klein [ 16/Apr/15 ] |
|
Issue has been found using fault injection, This is a low priority issue related to fit and finish, I'm closing this issue. |
| Comment by Robert Guo (Inactive) [ 22/Dec/14 ] |
|
stack trace |