[SERVER-39802] Write each applyOps in its own WUOW for unprepared commit on primary Created: 25/Feb/19  Updated: 14/May/19  Resolved: 14/May/19

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

Type: Task Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: Matthew Russotto
Resolution: Won't Fix Votes: 0
Labels: bigtxns_packing, bigtxns_perf
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39800 Investigate the new oplog format impa... Closed
Related
is related to SERVER-40797 Write each applyOps in its own WUOW f... Closed
Sprint: Storage NYC 2019-05-06, Repl 2019-05-20
Participants:

 Description   

We may need to split the single WUOW of unprepared transaction commit into smaller ones if it’s too large



 Comments   
Comment by Siyuan Zhou [ 09/May/19 ]

william.schultz, yes, like what we did for vectorized writes. Otherwise, majority writes will be blocked any (potentially very large) holes before them when waiting for write concern. Reads that wait for earlier oplog writes to be visible will also be affected.

Comment by William Schultz (Inactive) [ 09/May/19 ]

siyuan.zhou Are we splitting the large WUOW into smaller ones for performance reasons?

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