[SERVER-14233] Remove support for old oplog versions Created: 11/Jun/14  Updated: 27/Oct/15  Resolved: 25/Sep/14

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-4321 Document in Release Notes that suppor... Closed
Tested
Backwards Compatibility: Minor Change
Participants:

 Description   

In 2.2.1 we changed the oplog format to fix idempotency issues. We still have code in the server to handle old style oplog entries, it would be nice to get rid of that code now.

This could have implications for users who try to upgrade from some very old (before 2.2.1) version of mongodb up to 2.8. Even if they go through all intermediate versions (2.0->2.2->2.4->2.6->2.8), they will need to make sure that before going from 2.6 to 2.8 all nodes in the set have replicated past the last old style (pre 2.2.1) oplog entry, otherwise a 2.8 secondary will crash upon replicating an old style oplog entry.



 Comments   
Comment by Githook User [ 19/Sep/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-14233 remove support for old oplog versions
Branch: master
https://github.com/mongodb/mongo/commit/f69fefd9b7d9b2e19af32ab0337650a0fca3344a

Comment by Spencer Brody (Inactive) [ 25/Aug/14 ]

Moving to 2.7 required as otherwise we would have to re-implement this functionality in the new ReplicationCoordinatorImpl

Generated at Thu Feb 08 03:34:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.