[SERVER-8138] GridFS C++ client runs getLastError() against admin database Created: 10/Jan/13  Updated: 10/Dec/14  Resolved: 17/Sep/13

Status: Closed
Project: Core Server
Component/s: GridFS, Security, Sharding
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-8128 ShardConnection::sync() during autosp... Closed
Operating System: ALL
Steps To Reproduce:

Run a sharded cluster with auth and each shard with an admin user and use the GridFS.cpp client.

Participants:

 Description   

...which is a potential issue when using against authenticated 2.2.2 clusters (where GLE is required to be against the same database as the write operation). 2.3 and above use a different auth model, so the problem doesn't exist if newer mongoses/mongods are used. However, the problem should exist using the 2.4 client library against a 2.2 cluster.

(Note to reproduce on localhost an admin user is needed on the shards.)



 Comments   
Comment by Crystal Horn [ 17/Sep/13 ]

Only effects 2.4 client communicating with 2.2 server; no incident reports in over six months.

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