[SERVER-54792] Improve test coverage for insertMany on time-series collections with expireAfterSeconds Created: 25/Feb/21  Updated: 29/Oct/23  Resolved: 08/Mar/21

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

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

Issue Links:
Related
is related to SERVER-54921 Crash during concurrent ordered bulk ... Closed
is related to SERVER-54922 Crash (broken promise) with concurren... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-03-08, Execution Team 2021-03-22
Participants:

 Description   

Add concurrent test coverage for insertMany and expireAfterSeconds.

Original Description:

Steps to reproduce:

  1. create a TS collection with expireAfterSeconds 
  2. run an insertMany 
  3. inspect system.buckets collection and notice documents inserted
  4. refresh the collection and notice buckets have expired despite no matter the expireAfterSeconds

When creating a TS collection with expireAfterSeconds expireAfterSeconds param isn't being respected



 Comments   
Comment by Githook User [ 08/Mar/21 ]

Author:

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

Message: SERVER-54792 Add concurrency tests for bulk inserts on time-series collections concurrent with TTL deletions

This also adds slow operation logging for TTL deletions
Branch: master
https://github.com/mongodb/mongo/commit/a61cd4123668010637003b52b9f4644e499c5d16

Comment by Louis Williams [ 03/Mar/21 ]

I think whatever bug existed here has gone away. I will use this ticket to add some test coverage.

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