[SERVER-37976] Transaction coordinator should wait for writeConcern of majority commit point, not stable timestamp Created: 07/Nov/18  Updated: 05/Dec/18  Resolved: 04/Dec/18

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

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

Issue Links:
Duplicate
duplicates SERVER-37884 Coordinator should make its state dur... Closed
Related
related to SERVER-38094 Send prepareTransaction with write co... Closed
Sprint: Sharding 2018-12-03
Participants:

 Description   

It should also not pass a wTimeout so that it waits for writeConcern indefinitely (until stepdown or shutdown), and should invariant that no maxTimeMS is set on the OperationContext.



 Comments   
Comment by Esha Maharishi (Inactive) [ 04/Dec/18 ]

Will be done as part of adding an integration test for SERVER-37884 (otherwise the integration test would hang).

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