[SERVER-50483] Make donorStartMigration command check that the donor's host is not present in 'recipientConnectionString' Created: 24/Aug/20 Updated: 29/Oct/23 Resolved: 02/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-09-07 |
| Participants: |
| Description |
|
Improve this to also check that this donor's host is not present in 'recipientConnectionString' in the donorStartMigration command, and add a test case for that in jstests/replsets/tenant_migration_invalid_inputs.js. |
| Comments |
| Comment by Githook User [ 02/Sep/20 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com'}Message: |