[SERVER-40161] Make failure of conn->open_session in WiredTigerSession ctor non-fatal Created: 15/Mar/19  Updated: 06/Dec/22  Resolved: 02/Apr/20

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mira Carey Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40162 Change the default WiredTiger session... Closed
related to SERVER-30462 Coordinate connection and WT session ... Closed
is related to SERVER-17364 Idle cursors shouldn't hold storage e... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Making failures to allocate WiredTiger sessions non-fatal would offer a more graceful degradation than our current strategy (termination of the process).



 Comments   
Comment by Connie Chen [ 02/Apr/20 ]

If we run out of sessions, internal operations will be as likely to fail as user operations and its better to crash than to remain up in a degraded state, so we will not do this.

Comment by Mira Carey [ 15/Mar/19 ]

Yes. Well, not ignore, but throw instead of fassert

Comment by Eric Milkie [ 15/Mar/19 ]

To be precise, you want to ignore only the session-limit error returned from open_session(), and no other possible errors it may return, correct?

Comment by Mira Carey [ 15/Mar/19 ]

Back in SERVER-17364, we decided to keep failure to create WT_SESSION's fatal. Given that the main objection at that time had to do with choking on WT_SESSIONS for idle cursors (and that SERVER-17364 fixed that), I'd like to revisit whether we can make that non-fatal.

Generated at Thu Feb 08 04:54:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.