[SERVER-24560] Oplog as Buffer: Update BackgroundSync to use OplogBuffer instead of BlockingQueue Created: 14/Jun/16  Updated: 25/Jan/17  Resolved: 14/Jun/16

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
Backwards Compatibility: Fully Compatible
Sprint: Repl 16 (06/24/16)
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 15/Jun/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-24560 switched metrics.repl.buffer.maxSizeBytes from int to Counter64
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/ce7fc36d90b18b4e25e025bc3de613bde97973f1

Comment by Githook User [ 14/Jun/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-24560 replaced references to BlockingQueue in BackgroundSync with OplogBuffer

BackgroundSync now accepts an OplogBuffer at construction
Branch: master
https://github.com/mongodb/mongo/commit/0f744edcde0011533bc2d88b04581199cfee9070

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