[SERVER-24664] Get rid of calls to ShardingState::getCollectionMetadata Created: 20/Jun/16  Updated: 25/Oct/18  Resolved: 20/Jul/16

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Leon Zaruvinsky
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-23073 Aggregation checks the output collect... Closed
is depended on by SERVER-25061 Make CollectionShardingState a decora... Closed
Related
is related to SERVER-37750 Optimized $sample stage does not yield Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 16 (06/24/16), Sharding 17 (07/15/16), Sharding 18 (08/05/16)
Participants:

 Description   

The per-collection metadata is owned and managed through the CollectionShardingState class, which has one instance per sharded collection.

All retrieval of collection metadata should go through this class so it can enforce proper locking rules and we should remove calls to ShardingState::getCollectionMetadata, which does not check for locks.



 Comments   
Comment by Githook User [ 20/Jul/16 ]

Author:

{u'username': u'leonz', u'name': u'Leon Zaruvinsky', u'email': u'leon@mongodb.com'}

Message: SERVER-24664 Remove ShardingState::getCollectionMetadata, getVersion
Branch: master
https://github.com/mongodb/mongo/commit/0f21b1baf019d8c4edbce5e138ba809e6f6557ba

Comment by Githook User [ 22/Jun/16 ]

Author:

{u'username': u'leonz', u'name': u'Leon Zaruvinsky', u'email': u'leon@mongodb.com'}

Message: SERVER-24664 Get rid of calls to ShardingState::getCollectionMetadata
Branch: master
https://github.com/mongodb/mongo/commit/a009f41df2c3609b3c8dfd19ddc97ddbeef86984

Generated at Thu Feb 08 04:07:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.