[SERVER-6330] Can still perform unauthenticated queries after logging out on a replica set connection Created: 06/Jul/12  Updated: 15/Aug/12  Resolved: 11/Jul/12

Status: Closed
Project: Core Server
Component/s: Internal Client
Affects Version/s: 2.0.1, 2.1.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-6334 ReplSet connections magically gets re... Closed
Related
is related to SERVER-6117 SlaveOk Query fails with auth error e... Closed
Operating System: ALL
Participants:

 Comments   
Comment by Randolph Tan [ 11/Jul/12 ]

Test file removed updated test will be pushed in SERVER-6334.

Comment by Randolph Tan [ 11/Jul/12 ]

The issue of the secondary connections staying logged in after being logged out will also be addressed in SERVER-6334.

Comment by Randolph Tan [ 06/Jul/12 ]

Attached test file.

Cause: DBClientReplicaSet keeps separate connections for primary and secondary and issuing a logout command actually just logouts one of the connections.

Note: attached test only tests logout primary then query secondary. Should also add test for the opposite order.

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