ClusterSettings does not compute ClusterConnectionMode consistently

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • 5.0.0
    • Affects Version/s: None
    • Component/s: Configuration
    • None
    • Major Change
    • Needed
    • Hide

      Let's mention in What's new that we fixed the way ClusterConnectionMode is computed by ClusterSettings. ClusterSettings.getMode now consistently returns ClusterConnectionMode.MULTIPLE if the replica set name is configured, whether via ClusterSettings.Builder.applyConnectionString or via ClusterSettings.Builder. requiredReplicaSetName. Previously, this was happening only if the replica set name was configured via a connection string.

      Show
      Let's mention in What's new that we fixed the way ClusterConnectionMode is computed by ClusterSettings . ClusterSettings.getMode now consistently returns ClusterConnectionMode.MULTIPLE if the replica set name is configured, whether via ClusterSettings.Builder.applyConnectionString or via ClusterSettings.Builder. requiredReplicaSetName . Previously, this was happening only if the replica set name was configured via a connection string.
    • None
    • None
    • None
    • None
    • None
    • None

      The following code computes ClusterConnectionMode.MULTIPLE

      ClusterSettings.builder()
        .applyConnectionString(new ConnectionString("mongodb://127.0.0.1:27017/?replicaSet=replset"))
        .build()
        .getMode()

      but its direct counterpart that does not use applyConnectionString computes ClusterConnectionMode.SINGLE

      ClusterSettings.builder()
        .hosts(Collections.singletonList(
                new ServerAddress("127.0.0.1", 27017)
        ))
        .requiredReplicaSetName("replset")
        .build()
        .getMode()

            Assignee:
            Valentin Kavalenka
            Reporter:
            Valentin Kavalenka
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: