Arbiter Node Receiving High Application Connections in PSA Setup (MongoDB 8.x)

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Hi Team,

      We are currently running a PSA (Primary-Secondary-Arbiter) setup in our environment on MongoDB version 8.2.3. We have observed a high number of connections being established from the application to the arbiter node.

      As part of our validation:

       • We upgraded the arbiter to version 8.2.7
       • We downgraded the arbiter to version 8.0.12

      However, across all these versions, we continue to observe application connections being made to the arbiter node.

      We would like to understand whether this behaviour is expected (for example, due to topology discovery or monitoring by the drivers) or if this could be a known issue/bug in MongoDB 8.x versions.

      Driver Details:

       • spring-data-mongodb: 4.2.5
       • mongo-java-driver: 3.12.14
       • mongodb-driver-sync: 4.11.3
       • mongodb-driver-sync: 5.5.1
       • mongodb-driver-core: 5.5.1
       • bson-record-codec: 5.5.1
       • bson: 5.5.1
       • spring-boot-starter-data-mongodb: 3.5.6

      Could you please review and confirm:

       1. Whether application connections to the arbiter node are expected in this scenario
       2. Whether any driver-level configuration changes are required to prevent or reduce connections to the arbiter

      We appreciate your help on this.

            Assignee:
            Chris Kelly
            Reporter:
            Anand Amarnath C
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: