Operational Defect Database

BugZero found this defect 2565 days ago.

MongoDB | 355188

[SERVER-28040] Fix maxTimeMS/readPref/readConcern for sharded view query

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

3.4.2

Fixed releases:

3.5.6

Description:

Info

When a sharded query on a view with maxTimeMS is rewritten on mongos to a query over the view's backing collection, the maxTimeMS is discarded. The consequence is that the maxTimeMS is not enforced for a sharded queries over views. This is true for both views on sharded and unsharded collections. MaxTimeMS does work, however, for queries against a view delivered directly to mongod.

Top User Comments

xgen-internal-githook commented on Wed, 5 Apr 2017 17:51:44 +0000: Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'} Message: SERVER-28040 Fix maxTimeMS/readPref/readConcern for sharded view query Branch: master https://github.com/mongodb/mongo/commit/c3341d179db1c36722284676d99cb1c664fb1821

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:

...