Operational Defect Database

BugZero found this defect 2407 days ago.

MongoDB | 408260

[SERVER-30318] Sessions shouldn't require using legacy find path

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.5.11

Description:

Info

Sessions currently require forcibly using the OP_QUERY find path internally when fetching data to avoid recursively calling itself in the find command path. For SERVER-28509, I tagging all of the finds that force using OP_QUERY with a comment including this ticket.

Top User Comments

xgen-internal-githook commented on Mon, 31 Jul 2017 15:12:13 +0000: Author: {'email': 'randolph@10gen.com', 'username': 'renctan', 'name': 'Randolph Tan'} Message: SERVER-30318 Remove workaround for multiple instances of OperationContextSession per OperationContext Branch: master https://github.com/mongodb/mongo/commit/3cecc93793e62bc0451a04553e0ddb0df259fd1d renctan commented on Mon, 31 Jul 2017 15:06:54 +0000: cr: https://mongodbcr.appspot.com/145800001/ xgen-internal-githook commented on Fri, 28 Jul 2017 21:04:42 +0000: Author: {'email': 'randolph@10gen.com', 'username': 'renctan', 'name': 'Randolph Tan'} Message: SERVER-30318 Allow multiple instances of OperationContextSession per OperationContext Branch: master https://github.com/mongodb/mongo/commit/9abf0ffe9f50d069078b5cb708cc8aaf518f5405

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...