Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
Confidence Status:
None
Work Order:
3

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

If a call to getCollectionDescription is issued, we must make sure the collection information is known, that is, a refresh should've been called previously. If the data of the collection is unkown, throw a Stale Shard Version Exception. Make sure that all code paths are handling the exception appropriately.

depends on

SERVER-45780 Rename getCurrentMetadata to getCollectionDescription and change the return type

Closed

has to be done before

SERVER-45782 Remove usages of getCurrentShardVersionIfKnown and most of getCurrentMetadataIfKnown

Closed

is depended on by

SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"

Closed

SERVER-47412 Make the database cloner ensure collections are actually unsharded before cloning

Closed

SERVER-47413 Some transaction tests are not being retried on Transient Error

Closed

SERVER-47419 Find a better way of setting the shardId when throwing on getCollectionDescription

Closed

(1 is depended on by)

Assignee:: Marcos José Grillo Ramirez
Reporter:: Marcos José Grillo Ramirez
Participants:: Githook User, Marcos José Grillo Ramirez
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Jan 27 2020 12:40:46 PM UTC
Updated:: Oct 29 2023 10:12:52 PM UTC
Resolved:: Apr 08 2020 12:31:55 PM UTC
Confidence Status Last Update:: 03/Mar/20 10:07 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates