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

Java driver doesn't automatically discover replica set passive nodes

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.5
    • Component/s: Cluster Management
    • Labels:
      None
    • Operating System:
      ALL
    • # Replies:
      2
    • Last comment by Customer:
      true

      Description

      When creating a Mongo connection using "public Mongo( List<ServerAddress> replicaSetSeeds , MongoOptions options )" passive replica set members are not discovered and being added to the list automatically. It looks like ReplicaSetStatus$Node's update() method only looks at the "hosts" portion of the response, ignoring passives.

        Activity

        Hide
        antoine Antoine Girbal (Inactive) added a comment -

        fixed and tested.
        List of hosts will now be populated from both "hosts" and "passives".

        Show
        antoine Antoine Girbal (Inactive) added a comment - fixed and tested. List of hosts will now be populated from both "hosts" and "passives".
        Hide
        auto auto (Inactive) added a comment -

        Author:

        {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

        Message: JAVA-224: Java driver doesn't automatically discover replica set passive nodes
        https://github.com/mongodb/mongo-java-driver/commit/e62637fd20cef2cfe004b394bd1086d1570769be

        Show
        auto auto (Inactive) added a comment - Author: {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'} Message: JAVA-224 : Java driver doesn't automatically discover replica set passive nodes https://github.com/mongodb/mongo-java-driver/commit/e62637fd20cef2cfe004b394bd1086d1570769be

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since reply:
              4 years, 7 weeks, 6 days ago
              Date of 1st Reply: