[SERVER-29904] don't generate convertToCapped oplog entries Created: 28/Jun/17  Updated: 30/Oct/23  Resolved: 03/Jul/17

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

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-33183 Remove convertToCapped from OplogEntr... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-07-10
Participants:
Linked BF Score: 0

 Description   

convertToCapped is implemented as a temporary collection creation, insertion of all existing records and then rename-in-place. However, instead of using calling existing catalog-level operations and letting them deal with replication, convertToCapped has its own oplog entry and calls lower level operations directly while suppressing normal replication.

This adds extra maintenance work and upgrade complexities for supporting UUIDs. Removing the special purpose code simplifies, fixes some potential unhandled error conditions (WriteConflictException) and allows for normal rollback.



 Comments   
Comment by Githook User [ 03/Jul/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-29904 don't generate convertToCapped oplog entries
Branch: master
https://github.com/mongodb/mongo/commit/d362678ea9a9e4e948bfda0bc60e2fefdd1eb045

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