Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.8.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1645-Milestone-2

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-24, Sharding 2020-09-21
Linked BF Score:
50

This task is to implement the Collection cache on top of ReadThroughCache in order to make it causally consistent.

Ideally databases and collections should ideally be stored in two different cache objects and tracked independently and the retrieval of the Database + Collection combination for the unsharded case should be a syntactic sugar on top of it, rather than the current implementation, which stores them as two hierarchical caches.

causes

SERVER-50952 Ensure that cached collection entries with stale-marked shard will be eventually refreshed

Closed

depends on

SERVER-46154 Make ReadThroughCache be driven by a vector clock

Closed

SERVER-48990 Introduce ComparableChunkVersion class

Closed

SERVER-49190 Expose a function to iterate over all the entries in the ReadThroughCache

Closed

SERVER-50272 Make RoutingTableHistory movable

Closed

is depended on by

SERVER-50812 Remove the SetShardVersion command

Closed

SERVER-50815 Improve database and collection version formatting on logs

Closed

is duplicated by

SERVER-50042 Set shouldBlockBehindCatalogCacheRefresh to false on same thread as when set to true

Closed

split from

SERVER-48991 Make CatalogCache causally consistent

Closed

(2 is depended on by, 1 is duplicated by, 1 split from)

Assignee:: Tommaso Tocci

Reporter:: Kaloian Manassiev

Participants:: Githook User, Kaloian Manassiev, Tommaso Tocci

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Feb 15 2020 07:49:49 AM UTC

Updated:: Oct 29 2023 10:12:07 PM UTC

Resolved:: Sep 09 2020 10:54:04 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates