[SERVER-29270] oplog query for first entry should not use a blocking sort Created: 18/May/17  Updated: 30/Oct/23  Resolved: 31/May/17

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.4.11, 3.5.9

Type: Task Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Query 2017-06-19
Participants:
Linked BF Score: 0

 Description   

In certain cases this can cause us to lose our capped location due to oplog truncation in too_stale_secondary.js.



 Comments   
Comment by Githook User [ 01/Dec/17 ]

Author:

{'name': 'James Wahlin', 'username': 'jameswahlin', 'email': 'james@mongodb.com'}

Message: SERVER-29270 Oplog query for first/last entry should not use a blocking sort

(cherry picked from commit 3e8b9c599f3027778b48e8c3235d676134eef9bb)
Branch: v3.4
https://github.com/mongodb/mongo/commit/b7d69d885b54bb7583c24a09a6743cccabee7536

Comment by Githook User [ 31/May/17 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james@mongodb.com'}

Message: SERVER-29270 Oplog query for first/last entry should not use a blocking sort
Branch: master
https://github.com/mongodb/mongo/commit/3e8b9c599f3027778b48e8c3235d676134eef9bb

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