[SERVER-62482] Use recipientTagName to identify recipient nodes merge Created: 10/Jan/22  Updated: 29/Oct/23  Resolved: 04/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Didier Nadeau Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-02-07
Participants:
Linked BF Score: 42

 Description   

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



 Comments   
Comment by Githook User [ 04/Feb/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-62482 Build recipient connection string from tag/set name
Branch: master
https://github.com/mongodb/mongo/commit/2e878f0d1f4234199fe0602878de0ac1ce7aa0cc

Generated at Thu Feb 08 05:55:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.