[SERVER-35024] atClusterTime erroneously chooses round_to_oldest option Created: 16/May/18  Updated: 29/Oct/23  Resolved: 18/May/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-05-21
Participants:

 Description   

This can result in incorrect data being returned when using atClusterTime read concern.



 Comments   
Comment by Githook User [ 18/May/18 ]

Author:

{'username': 'louiswilliams', 'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com'}

Message: SERVER-35024 Fix typo
Branch: master
https://github.com/mongodb/mongo/commit/c935b06fab9dc1024ea87908b266a07db73fa595

Comment by Githook User [ 18/May/18 ]

Author:

{'username': 'louiswilliams', 'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com'}

Message: SERVER-35024 atClusterTime incorrectly uses round_to_oldest option when opening transactions. Refactor WiredTigerBeginTxnBlock to use enum parameters with safe defaults.
Branch: master
https://github.com/mongodb/mongo/commit/355e76896cdd365983fcf8393da967ca8765fe3b

Comment by Louis Williams [ 16/May/18 ]

The second argument to WiredTigerBeginTxnBlock::setTimestamp() is a bool, roundToOldest. This line of code is passing a pointer, which is implicitly casting it to a true bool.

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