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

Invariant failure | aborting after invariant

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Query Execution 2021-02-22, Query Execution 2021-03-08, Query Execution 2021-03-22

      Description

      I have recently upgraded my MongoDB server from 4.2.1 to 4.4.3 to utilize some new features. Since then I am consistently facing the issue of mongod service failure.

      I have been searching for any solution available for a couple of days but unfortunately couldn't find one. Below are my logs which took out right after my mongod service got failed.

      "ctx":"conn17583","msg":"Slow query","attr":{"type":"command","ns":"staging_reflecx_io.org","command":{"aggregate":"org","pipeline":[{"$match":{"level":1,"_id":{"$in":[{"$oid":"5fcf7998b5c4c43ed8bffb85"}]}}},{"$graphLookup":{"from":"org","startWith":"$_id","connectFromField":"_id","connectToField":"parent_id","as":"dealerhierarchy"}},{"$unwind":"$dealerhierarchy"},{"$match":{"dealerhierarchy.level":5}},{"$group":{"_id":null,"count":{"$sum":1},"dealers":{"$push":"$dealerhierarchy._id"}}}],"cursor":{},"$db":"staging_reflecx_io","lsid":{"id":{"$uuid":"1907851c-f708-4dbd-8209-af5cb84f3347"}}},"planSummary":"IXSCAN { _id: 1 }","keysExamined":1,"docsExamined":1,"cursorExhausted":true,"numYields":72,"nreturned":1,"queryHash":"F9571571","planCacheKey":"7EBE716A","reslen":13843,"locks":{"ReplicationStateTransition":{"acquireCount":{"w":95}},"Global":{"acquireCount":{"r":95}},"Database":{"acquireCount":{"r":95}},"Collection":{"acquireCount":{"r":96}},"Mutex":{"acquireCount":{"r":23}}},"storage":{},"protocol":"op_msg","durationMillis":3202}}
      {"t":{"$date":"2021-02-04T02:30:12.410-05:00"},"s":"F", "c":"-", "id":23079, "ctx":"conn17454","msg":"Invariant failure","attr":{"expr":"valueSize <= _memoryUsage","file":"src/mongo/db/pipeline/lookup_set_cache.h","line":141}}
      {"t":{"$date":"2021-02-04T02:30:12.410-05:00"},"s":"F", "c":"-", "id":23080, "ctx":"conn17454","msg":"\n\n***aborting after invariant() failure\n\n"}
      {"t":{"$date":"2021-02-04T02:30:12.410-05:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"conn17454","msg":"Writing fatal message","attr":{"message":"Got signal: 6 (Aborted).\n"}}

      Can you please explain why this service is getting failed or being killed? As my server was working perfectly fine when I was on 4.2.1

        Attachments

        1. 1111.PNG
          1111.PNG
          8 kB
        2. 2222.PNG
          2222.PNG
          5 kB
        3. image-2021-02-05-03-31-32-930.png
          image-2021-02-05-03-31-32-930.png
          30 kB
        4. image-2021-02-08-16-38-53-529.png
          image-2021-02-08-16-38-53-529.png
          36 kB

          Activity

            People

            Assignee:
            arun.banala Arun Banala
            Reporter:
            abdulmoiz.baig.work@gmail.com am z
            Participants:
            Votes:
            3 Vote for this issue
            Watchers:
            16 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: