[SERVER-79309] Port SERVER-77538 to Shard Role acquisitions Created: 25/Jul/23 Updated: 27/Oct/23 Resolved: 16/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18, Execution EMEA Team 2023-10-02, Execution EMEA Team 2023-10-16, Execution EMEA Team 2023-10-30 | ||||||||
| Participants: | |||||||||
| Description |
|
The ticket in question fixes a problem on the legacy AutoGet* classes. Shard Role acquisitions copied the old logic and should get it fixed as well. |
| Comments |
| Comment by Jordi Olivares Provencio [ 16/Oct/23 ] |
|
Closing as Works as Designed since the error simply cannot occur in acquisitions. The problem described is an issue only with the legacy approach. In that case we perform an acquisition with a namespace but then restore using the UUID. This can be an issue with the catalog since it wouldn't find the correct collection and falsely report an error. However, acquisitions use the namespace instead and then use the UUID obtained at the beginning to verify the collection is still the same. This means that the error described is impossible and cannot occur on acquisitions. |