[SERVER-42645] MigrationDestinationManager should use uuid strings instead of ns strings with moveParanoia Created: 06/Aug/19 Updated: 06/Dec/22 Resolved: 30/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
With the removal of collection name lengths, migrations should not use the collection name to store moveChunk data with moveParanoia on, but should rather use the collection UUID as we cannot create directories on the file system with very long names. See here |
| Comments |
| Comment by Ratika Gandhi [ 30/Aug/19 ] |
|
Requires more context and we are not sure if this needs to fixed. |