[SERVER-21031] Vectorize logOp Created: 20/Oct/15  Updated: 06/Dec/22  Resolved: 12/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.0-rc2

Type: Improvement Priority: Major - P3
Reporter: Martin Bligh Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Make logOp (on the primary) write to the oplog in vectors when possible, not one element at a time - for efficiency



 Comments   
Comment by Githook User [ 28/Oct/15 ]

Author:

{u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}

Message: SERVER-21031: Vectorize logOps
Branch: master
https://github.com/mongodb/mongo/commit/335333bccd09e8eb7d0184147eb1647200ce6711

Comment by Githook User [ 27/Oct/15 ]

Author:

{u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}

Message: Revert "SERVER-21031: Vectorize logOps"

This reverts commit bc0704481b68db6d3116eb2692088f73759d776a.
Branch: master
https://github.com/mongodb/mongo/commit/45bfa34b8b99237c16a839e5afa0df44c5fde15d

Comment by Githook User [ 27/Oct/15 ]

Author:

{u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}

Message: SERVER-21031: Vectorize logOps
Branch: master
https://github.com/mongodb/mongo/commit/bc0704481b68db6d3116eb2692088f73759d776a

Comment by Martin Bligh [ 22/Oct/15 ]

insertMulti, and in the middle of converting writeCmd insert to do the same

Comment by Andy Schwerin [ 22/Oct/15 ]

Yeah. How often are there multiple logops on the primary in the same WUOW? I can't think of any, given the current implementation of the higher level operations.

Comment by Martin Bligh [ 22/Oct/15 ]

As long as it's in the same WUOW, I believe it's OK?

Comment by Andy Schwerin [ 22/Oct/15 ]

Under what circumstances might this be possible? The oplog write must occur atomically with the document write, today, which would seem to make this change pretty invasive.

Comment by Andy Schwerin [ 21/Oct/15 ]

Can you add a little description please?

Comment by Githook User [ 20/Oct/15 ]

Author:

{u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}

Message: SERVER-21031: Rename the function that doesn't create the oplog to something other than createOplog
Branch: master
https://github.com/mongodb/mongo/commit/6e4c71f1d742439e1959fedc1b2177ddc9306fdb

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