[SERVER-20694] user-initiated finds against the config servers can fail with "need to swap catalog manager" error Created: 29/Sep/15  Updated: 25/Jan/17  Resolved: 07/Jan/16

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: 3.1.8
Fix Version/s: 3.2.3, 3.3.0

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: code-and-test, csrsupgrade, disabled-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding B (10/30/15), Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16)
Participants:
Linked BF Score: 0

 Description   

User-initiated finds on the "config" or "admin" dbs may fail with "need to swap catalog manager".

We need to either make the find and getmore commands run by the new find command code run through the catalog manager (which may be quite difficult), or just accept this state and require users to retry their queries in these cases.



 Comments   
Comment by Githook User [ 14/Jan/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20694 Catch IncompatibleCatalogManager errors in cluster find code

(cherry picked from commit afadb50a096e27158cab38d2eb2bd3e445b09eab)
Branch: v3.2
https://github.com/mongodb/mongo/commit/4a9123577a4aac9ab3e14bddb519d61082dc2101

Comment by Githook User [ 07/Jan/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20694 Catch IncompatibleCatalogManager errors in cluster find code
Branch: master
https://github.com/mongodb/mongo/commit/afadb50a096e27158cab38d2eb2bd3e445b09eab

Comment by Githook User [ 28/Oct/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-20694 Wait for nodes to catch up in csrs_upgrade.js by monitoring replSetGetStatus.

The original trick of doing a write with write concern

{ w:csrs.length }

is not legal
after SERVER-20891.
Branch: master
https://github.com/mongodb/mongo/commit/4727903fd65590855186979e5d3967784b1a5f94

Comment by Githook User [ 28/Oct/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-20694 Do not require w:majority on writes to config replica sets in SCCC mode.
Branch: master
https://github.com/mongodb/mongo/commit/5fcf227019e365e3ddc81a4ea5db97ab0cef4c33

Comment by Spencer Brody (Inactive) [ 06/Oct/15 ]

Moving back into 3.1 Required so we at least take another look at csrs_upgrade.js and ensure we haven't totally broken our ability to support upgrade going forward.

Comment by Githook User [ 29/Sep/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20694 Temporarily disable csrs_upgrade.js test
Branch: master
https://github.com/mongodb/mongo/commit/2df922eae05292e9ec5b5e4d2525d3c429a8ea4f

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