[SERVER-36537] Initial sync cursor should not keep data in cache Created: 08/Aug/18  Updated: 29/Oct/23  Resolved: 13/Dec/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.7

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36068 Expose a user-accessible cursor optio... Closed
Duplicate
is duplicated by SERVER-42466 use read_once cursor option during in... Closed
Related
is related to SERVER-47055 Investigate performance regression in... Closed
is related to SERVER-47056 Do not use readOnce cursors for colle... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-11-19, Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14
Participants:

 Description   

This will be accomplished by passing the query option provided inĀ SERVER-36068.



 Comments   
Comment by Githook User [ 13/Dec/18 ]

Author:

{'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}

Message: SERVER-36537 Initial sync cursor should not keep data in cache.
Branch: master
https://github.com/mongodb/mongo/commit/c1954ac6bdb34c22274d70e8fabbd04555ec7bb2

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