[SERVER-36334] Disallow setting "h" field in oplog entries Created: 27/Jul/18  Updated: 29/Oct/23  Resolved: 25/Aug/22

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.5 Required
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Suganthi Mani Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-36815 Remove the references of hash field o... Closed
is related to SERVER-69062 Fully remove 'h' field from oplog ent... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2022-09-05
Participants:

 Description   

"h" field is used to differentiate oplog entries with same timestamp. Its useful only for pv0. Since in pv1, our oplog entry optime consists of ts + term, "h" field is really not needed in pv1.



 Comments   
Comment by Britt Snyman [ 01/Sep/22 ]

Replacing the 6.1.0-rc1 fixVersion with 6.2.0-rc0 since these tickets had commits to master that were merged after we branched for v6.1.

Comment by Githook User [ 25/Aug/22 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-36334 Discontinue setting 'h' field in oplog entries
Branch: master
https://github.com/mongodb/mongo/commit/c34ead5d76f2f6c5c87a14ce90d9983b02e64ed4

Comment by Judah Schvimer [ 05/Aug/22 ]

This continues to cause confusion, we should reconsider doing this code cleanup.

Comment by Charles Kalmanek [ 20/Apr/20 ]

This is relevant to Mongomirror, which may need to take special action when migrating from an older to newer server version.

Comment by Siyuan Zhou [ 20/Apr/20 ]

We also need to consider the impact on applyOps command - whether providing the "h" field will cause an error.

Comment by Tess Avitabile (Inactive) [ 31/Jul/18 ]

We would have to remove this field over two releases (making it optional in the IDL in this release, and removing it in the next release), unless we decide not to do strict field checking for oplog entries.

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