Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1965-Cleanup

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17
Linked BF Score:
165
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The goal of this ticket is to relax the implementation of the getDatabaseWithRefresh and the getCollectionRoutingInfoWithRefresh methods: both of them invalidate an entry in their caches.

Instead of doing that, we could just advanceTimeInStore using a ComparableDatabaseVersion/ComparableChunkVersion with the forcedRefresh flag.

Some tests, for instance this one, will have to be fixed.

depends on

SERVER-56469 The shard server catalog cache loader should replace the entries on config.cache.collections and not just update them

Closed

SERVER-53861 Implement stop migrations procedure for DDL operations

Closed

SERVER-55146 Bump collection version on any modification of config.collections reshardingFields or allowMigrations fields

Closed

Assignee:: Sergi Mateo Bellido
Reporter:: Sergi Mateo Bellido
Participants:: Githook User, Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Feb 17 2021 06:12:05 AM UTC
Updated:: Oct 29 2023 09:57:25 PM UTC
Resolved:: May 06 2021 12:37:36 PM UTC
Confidence Status Last Update:: 29/Apr/21 10:38 AM