Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70783

WT_ERROR: non-specific WiredTiger error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • None
    • None
    • None
    • ALL

    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

      Attachments

        Activity

          People

            Unassigned Unassigned
            manoshmalai@gmail.com Mano malai
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: