PoolClearedError randomly appears

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • Not Needed
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      I'm currently experiencing a frustrating "bug". I've this error randomly appearing :
      PoolClearedError [MongoPoolClearedError]: Connection pool for ....com:27017 was cleared because another operation failed with: "connection <monitor> to [...::]:27017 timed out"

      Environment

      • Nodejs v18.15.0
      • mongoose v7.3.1
      • mongodb v6.0.6

      -Debian 11

      • Replica set with 2 nodes (self hosted)

      How to Reproduce

      • I have sadly no idea about how to reproduce :/ My server is clearly not overloaded :
        and the bug randomly pop out.

      Additional Background

      I'm running my code as usual, and this error comes sometimes after 5 our 6 hours, sometimes 2 minutes after i start my process

        1. image-2023-06-30-11-06-11-835.png
          image-2023-06-30-11-06-11-835.png
          73 kB

            Assignee:
            Unassigned
            Reporter:
            Johan Maupetit
            None
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: