[SERVER-70783]  WT_ERROR: non-specific WiredTiger error Created: 22/Oct/22  Updated: 25/Oct/22  Resolved: 25/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Mano malai Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

We have MongoDB 4 Shard Cluster, One particular shard getting crash after throwing the below error everyday couple of time.

  1. 2022-10-12T18:25:28.760+0530 I NETWORK  [conn93431] received client metadata from 10.241.89.33:60354 conn93431: { driver: { name: "NetworkInterfaceTL", version: "4.0.28" }, os: { type: "Linux", name: "Red Hat Enterprise Linux release 8.5 (Ootpa)", architecture: "x86_64", version: "Kernel 4.18.0-348.20.1.el8_5.x86_64" } }

  1.   2022-10-12T18:25:29.271+0530 E STORAGE  [conn93431] WiredTiger error (-31802) [1665579329:271730][4154273:0x7efde3939700], WT_CONNECTION.open_session: __open_session, 2058: out of sessions, configured for 20030 (including internal sessions): WT_ERROR: non-specific WiredTiger error Raw: [1665579329:271730][4154273:0x7efde3939700], WT_CONNECTION.open_session: __open_session, 2058: out of sessions, configured for 20030 (including internal sessions): WT_ERROR: non-specific WiredTiger error
    
    

  1. 2022-10-12T18:25:29.271+0530 F -        [conn93431] Invariant failure: conn->open_session(conn, NULL, "isolation=snapshot", &_session) resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src/mongo/db/storage/wiredtiger/wiredtiger_session_cache.cpp 111

  1. 2022-10-12T18:25:29.271+0530 F -        [conn93431] \n\n***aborting after invariant() failure\n\n

     
    MongoDB Version: 4.0.28



 Comments   
Comment by Yuan Fang [ 25/Oct/22 ]

Hi manoshmalai@gmail.com,

Thank you for your report. MongoDB Version 4.0 reached end of life in April 2022 and is no longer supported. Would you please upgrade to MongoDB v4.2+ and see if it solves the issue?

Suppose the issue still existed after upgrading to the supported version. In that case, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.

If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Regards,
Yuan

Generated at Thu Feb 08 06:17:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.