Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41602

Activate followBusiestNode in ShardingTaskExecutor

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0-rc2, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.2
    • Service Arch 2019-06-17, Service Arch 2019-07-01
    • 20

      As is, the fBN mode has problems with decreasing its connection target. I've spun this out as a separate ticket to land followPrimaryNode more quickly.

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: