[SERVER-66390] CollMod should take distlock on timeseries bucket ns Created: 11/May/22 Updated: 06/Dec/22 Resolved: 28/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | timeseries_DDL_bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
and stop migration on it as well. When running collMod against a timeseries collection, we use the original ns (view ns) when creating the coordinator doc (and this gets used by the ddl coordiantor to take dist locks). It also uses the original ns when stopping migrations here |
| Comments |
| Comment by Cris Insignares Cuello [ 12/May/22 ] |
|
|