[SERVER-45781] Throw Stale Shard Version when collection is unknown on getCollectionDescription Created: 27/Jan/20  Updated: 29/Oct/23  Resolved: 08/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45780 Rename getCurrentMetadata to getColle... Closed
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
is depended on by SERVER-47412 Make the database cloner ensure colle... Closed
is depended on by SERVER-47413 Some transaction tests are not being ... Closed
is depended on by SERVER-47419 Find a better way of setting the shar... Closed
Gantt Dependency
has to be done before SERVER-45782 Remove usages of getCurrentShardVersi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-45781 Throw Stale Shard Version when collection is unknown on getCollectionDescription and renamed old version to getCollectionDescription_DEPRECATED
Branch: master
https://github.com/mongodb/mongo/commit/e93a19b0d6c3e7004efd914a5e6dd27bc525c421

Generated at Thu Feb 08 05:09:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.