[SERVER-17723] Sharding catalog cache Created: 24/Mar/15  Updated: 19/Sep/15  Resolved: 10/Apr/15

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

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

Issue Links:
Depends
is depended on by SERVER-17917 Config DB gets updated even though th... Closed
Related
is related to SERVER-18062 Creating an index on a collection in ... Closed
is related to SERVER-18047 Explain on non-existent database shou... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding 1 04/03/15, Sharding 2 04/24/15
Participants:

 Description   

This task is to build a sharding catalog cache on top of the CatalogManager abstraction and use this in place of the direct network calls to the config server.



 Comments   
Comment by Githook User [ 10/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Sharding catalog cache

This change builds a sharding catalog cache on top of the CatalogManager
abstraction and use this in place of the direct network calls to the
config server.
Branch: master
https://github.com/mongodb/mongo/commit/8e6804d268895c01678a1a3d2feb57a82cafec62

Comment by Githook User [ 10/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 rename7.js should pre-create database

Otherwise it fails when sharding is made to not create database entries
for read operations.
Branch: master
https://github.com/mongodb/mongo/commit/1cecc679bfb414f90e33cc0c0c6ed292667925fe

Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Clean up the list_indexes test
Branch: master
https://github.com/mongodb/mongo/commit/91d669830d1cb04d9a35992092a3eb139dd5c9f8

Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Fix clone_as_capped_nonexistant.js
Branch: master
https://github.com/mongodb/mongo/commit/03fe2ccb8162a27dc4b311306df91f65e2f639bc

Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 NamespaceNotFound -> DatabaseNotFound

DatabaseNotFound is more descriptive for the actual error condition.
Branch: master
https://github.com/mongodb/mongo/commit/a906fc2423f09bab7213e2448549d1dd28001534

Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Remove 'source' from the error message for collectionToCapped'

Helps unify the error messages returned for mising collections between
sharded and non-sharded cluster. Besides there is no source and
destination database for these two commands.
Branch: master
https://github.com/mongodb/mongo/commit/c64199204eb3873cd87784efaed440afc3d66f94

Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Split explain_null_collection test into two tests
Branch: master
https://github.com/mongodb/mongo/commit/221772437968c316bc842e7899950d746eac755e

Comment by Githook User [ 08/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Change explain_read_pref.js to use an existing database
Branch: master
https://github.com/mongodb/mongo/commit/04a120d6dc50d6bb1fd5073ea28a6c8ddc07fecd

Comment by Githook User [ 07/Apr/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 Make the move_primary_ignore_sharded.js test more readable
Branch: master
https://github.com/mongodb/mongo/commit/cbc6bc3c72bf7472b112a6782c76ba2ea3fa1ad7

Comment by Githook User [ 31/Mar/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17723 setShardingState should not reinitialize config servers list

Currently we reinitialize the list after stepdown, but this is not
necessary, because the config servers should never change and in addition,
this causes problems with code which assumes once-only initialization.
Branch: master
https://github.com/mongodb/mongo/commit/14ce8911246fa6a9ae238d69fac05b169a66e6d4

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