Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-2891

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

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

      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 Unassigned
            Reporter:
            chambec4 Cory Chamberlain
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: