[SERVER-35187] Off by one error in transaction reaper Created: 23/May/18  Updated: 29/Oct/23  Resolved: 01/Jun/18

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Sarah Zhou
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-06-04, Sharding 2018-06-18
Participants:

 Description   

When handling expired transaction table entries, the transaction reaper handles each individually and bundles their session ids into a batch to be removed all at once. If the number of session ids in the current batch is greater than the max write batch size, handling will be paused and the accumulated sessions will be removed from the transaction table (if their corresponding session collection records have already been deleted). The session entries should instead be removed when the number of ids is equal to the max batch size. This is the case for both the sharded and replica set handlers.



 Comments   
Comment by Githook User [ 01/Jun/18 ]

Author:

{'name': 'Sarah Zhou', 'email': 'sarahzhou@MacBook-Pro-80.local'}

Message: SERVER-35187 fix off by one error in transaction reaper
Branch: master
https://github.com/mongodb/mongo/commit/5d136ba87381fc09608c69cd6036c6c2298e1d8f

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