[SERVER-79964] Shards participating in the authoritative shardCollection should have up-to-date filtering information before the critical section is released Created: 14/Aug/23 Updated: 30/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Pol Pinol |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | authoritative-create-collection | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Sprint: | Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-18 | ||||||||
| Participants: | |||||||||
| Description |
|
Today the authoritative version of shardCollection performs a best-effort step to flush the metadata caches on non primary shards. A synchronous version of the same step (like in this example) would guarantee "truly authoritative" properties to the whole DDL. |