The JAVA driver does not reconnect after a rebuild and init of a replica set

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.4.2
    • Component/s: Connection Management
    • None
    • Environment:
      RHEL 7.2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are using a 3 member replica set (1 member is an arbiter). If we restart the primary mongod instance our java applications reconnect correctly when a new primary is available, however if we rebuild (delete all mongodb data) and initialize the replica set none of our java applications are able to reconnect unless we restart them (not desirable).  We're creating the MongoClient with a list of ServerAddress (3 servers) and we set the serverSelectionTimeout and connectTimeout options (both set to 3 seconds).  We have the same problem with the C++ driver (3.1.1 version).

            Assignee:
            Unassigned
            Reporter:
            Cory Chamberlain
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: