[SERVER-49698] Smarter causal consistent CatalogCache refresh Created: 17/Jul/20 Updated: 31/Jul/20 Resolved: 31/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Randolph Tan | Assignee: | Tommaso Tocci |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
We currently achieve causal consistency by forcing another refresh here: https://github.com/mongodb/mongo/blob/r4.4.0-rc12/src/mongo/s/catalog_cache.cpp#L324 However, it is possible to improve this if we know the clusterTime when the refresh was requested and the some indication of how "fresh" the cache is in terms of clusterTime. |
| Comments |
| Comment by Kaloian Manassiev [ 21/Jul/20 ] |
|
renctan, I think this is a duplicate of |