Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-5988

MongoDB Compass causes the replicaset primary to crash

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: 1.32.5
    • Component/s: Compass
    • None
    • Environment:
      Replicaset running on Ubuntu 18
      MongoDB Compass running MacOS BigSur 11.6 with Intel
    • Not Needed

      Problem Statement/Rationale

      Connecting to replicaset using MongoDB Compass causes the primary to crash.

      Please be sure to attach relevant logs with any sensitive data redacted.

      Steps to Reproduce

      Create a replicaset of 3 nodes, mongo version 5.0.9 community.

      Connect to the replicaset using MongoDB compass version 1.32.5, using direct connect.

      Expected Results

      MongoDB Compass should connect successfully and display the collections. The replicaset primary should handle the connection and queries from MongoDB Compass without any significant load.

      Actual Results

      The amount of file descriptors (possible due to connections and queries) spikes in order of tens of thousands. This leads to too many files open and eventually a primary crash. Meanwhile this is happening, MongoDB Compass hangs and shows a blank screen.

      Additional Notes

      The database that causes MongoDB Compass to hang and the primary to crash weight about 4 terrabytes. We are using the direct connect option because we're opening an SSH tunnel from our local machines to the primary using a jumper server.

            Assignee:
            Unassigned Unassigned
            Reporter:
            nivi.mor@bigpanda.io Nivi Mor
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: