[SERVER-53999] Time-series buckets often close due to time moving backward with concurrent writers Created: 22/Jan/21  Updated: 29/Oct/23  Resolved: 05/Feb/21

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-02-08
Participants:

 Description   

When there are concurrent writers inserting into a time-series collection, the writers racing to call BucketCatalog::insert causes these inserts to be out of order of the times specified by the timeField. Since we always close a bucket if time moves backward, we end up closing many buckets this way that otherwise would not need to be closed. We should find a way to mitigate this behavior so that we don't end up with many small buckets.



 Comments   
Comment by Githook User [ 05/Feb/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-53999 Allow a time-series bucket's id to move backward before being committed
Branch: master
https://github.com/mongodb/mongo/commit/11cdc521135cd8ad49136a4bfbc9f873ca519537

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