[SERVER-29127] Improve behavior of tailable awaitData cursors with readConcern:majority Created: 11/May/17  Updated: 30/Oct/23  Resolved: 24/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Crystal Horn 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-29126 Require change streams to run with re... Closed
Related
related to SERVER-31606 Primary removes drop-pending collecti... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-08-21, Repl 2017-09-11
Participants:
Linked BF Score: 0

 Comments   
Comment by Ramon Fernandez Marina [ 24/Aug/17 ]

Author:

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

Message:SERVER-29127 Improve behavior of tailable awaitData cursors with readConcern:majority

Fixes a bug with awaitData cursors on readConcern:majority; they would not be awakened when a new
snapshot was set to "committed". Also removed a related false comment.

Fixes a bug in planExecutor which would prevent awakening when oplog visibility changed with
a visibility-restricted cursor active.
Branch:master
https://github.com/mongodb/mongo/commit/d000511fe6e12657da536648317865915c03123a

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