Use recipientTagName to identify recipient nodes merge

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Server Serverless 2022-02-07
    • 42
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently use an outdated recipientConnectionString to identify and monitor recipient nodes for the split operation. In production we will instead use a recipientTagName provided by cloud to target nodes in our local configuration as recipient nodes.

      Waiting on SERVER-62018

            Assignee:
            Matt Broadstone
            Reporter:
            Didier Nadeau
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: