[SERVER-69887] The getCollectionDescription doesn't represent static collection information anymore Created: 22/Sep/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Thus, it should have exactly the same synchronization conditions that we have for the getMetadataWithCheck method, e.g. honouring the critical section. We should consider to backport this until 5.0, before that version we had few fields associated to the collection. |
| Comments |
| Comment by Jordi Serra Torrens [ 29/Jun/23 ] |
|
Moving to PM-2948 since it will make the shards authoritative for the description. As part of that, it will make the description only change under the critical section. At that point, it will make sense to synchronize getCollectionDescription with the critical section. |