Primary member is detected as UNKNOWN at mongo client side

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Declined
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.12.9
    • Component/s: None
    • None
    • 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

      We have multiple instances of applications running, each will do db transactions.

      After our application installation, we could see continuous db transaction failures in one of the application instance and could see the below errors from that instance alone,

      binding-s107  2023-10-31 07:47:36,514 [pool-66-thread-1] DEBUG org.mongodb.driver.protocol.command - Execution of command with request id 188706247 completed successfully in 20.60 ms on connection [connectionId\{localValue:132588, serverValue:23}] to server 2606:ae00:3001:8311:172:16:244:60:27040
      binding-s107  2023-10-31 07:47:36,514 [pool-65-thread-1] INFO  org.mongodb.driver.cluster - Invalidating potential primary 2606:ae00:3001:8311:172:16:244:60:27040 whose (set version, election id) tuple of (23, 7fffffff0000000000000016) is less than one already seen of (24, 7fffffff0000000000000015)
      _binding-s107  2023-10-31 07:47:36,515 [pool-65-thread-1] DEBUG org.mongodb.driver.cluster - Updating cluster description to  {type=REPLICA_SET, servers=[

      {address=2606:ae00:3001:8311:172:16:244:b9:27040, type=REPLICA_SET_ARBITER, roundTripTime=20.8 ms, state=CONNECTED}

      , {address=2606:ae00:3001:8311:172:16:244:a9:27040, type=REPLICA_SET_ARBITER, roundTripTime=20.6 ms, state=CONNECTED}, {address=2606:ae00:3001:8311:172:16:244:60:27040, type=UNKNOWN, state=CONNECTING},........_

      Db transactions from other application instances are success.

      Mongo version:

      Mongo Server: 5.0

      Client: 3.12.9

      How to Reproduce

      It occurred only once after our application upgrade.

       

            Assignee:
            Unassigned
            Reporter:
            senthil kumar c
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: