[SERVER-36130] Migration status reports verify connection strings -- but those can change Created: 13/Jul/18 Updated: 29/Oct/23 Resolved: 28/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | 4.0.3, 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Sharding 2018-09-10 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 17 | ||||||||
| Description |
|
During the chunk migration process, the source shard periodically polls the destination shard for updates. As part of the information verification process, we verify that the source shard's connection string hasn't changed. However, valid situations exist where it might change. For example, adding a new node to the source shard's replica set would change the connection string but would not change the behavior of that shard with regards to migrations. Failures have cropped up where shards are aborted because the connection string has changed. Instead, we should verify that the from shard's name hasn't changed. Shard names are immutable and will serve to verify a shard without error. The line of code to change is here. |
| Comments |
| Comment by Githook User [ 21/Sep/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: (cherry picked from commit 1ee551653a1ff9c154d94e59c429529eb3ea9098) |
| Comment by Githook User [ 28/Aug/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |