[SERVER-60378] Rewrite some sharding tests to avoid using chunk versions with Timestamp(0, 0) Created: 01/Oct/21  Updated: 29/Oct/23  Resolved: 08/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0, 5.1.0-rc2

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.1
Sprint: Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Participants:
Linked BF Score: 46

 Description   

Timestamp(0, 0) has a special meaning (i.e. get the current time) as we saw in BF-22784.

Since we are not actually creating collections with this timestamp the goal of this ticket is to revisit the tests changed in SERVER-52847, changing the default constructed timestamps by a valid one.



 Comments   
Comment by Githook User [ 22/Oct/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-60378 Rewrite some sharding tests to avoid using chunk versions with Timestamp(0, 0)

(cherry picked from commit 8679a54bd8780fdbe1cb6a052f70a494cd4205e5)
Branch: v5.1
https://github.com/mongodb/mongo/commit/76e0c9ffab85201ee1a02a70584cf758695c6629

Comment by Githook User [ 08/Oct/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-60378 Rewrite some sharding tests to avoid using chunk versions with Timestamp(0, 0)
Branch: master
https://github.com/mongodb/mongo/commit/8679a54bd8780fdbe1cb6a052f70a494cd4205e5

Comment by Sergi Mateo Bellido [ 06/Oct/21 ]

Before I forget: we will need to backport these changes to 5.1

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