[SERVER-64199] Routing performance benchmarks use default Timestamp for the collection Created: 04/Mar/22  Updated: 29/Oct/23  Resolved: 07/Mar/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.0.0-rc0, 5.3.0-rc3

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-62684 Get rid of usages of ChunkVersion::ep... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.3
Sprint: Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
Participants:
Linked BF Score: 52

 Description   

The routing performance benchmarks use default Timestamp when instantiating a mocked routing info for the collection, which is invalid.



 Comments   
Comment by Githook User [ 07/Mar/22 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-64199 Use legal Timestamps for the routing performance benchmarks

(cherry picked from commit 7e114c6dc901142c721a9ca7c7adc17edd4868e4)
Branch: v5.3
https://github.com/mongodb/mongo/commit/29371ed11e06b9e85f93e981986c0efceac0df40

Comment by Githook User [ 07/Mar/22 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-64199 Use legal Timestamps for the routing performance benchmarks
Branch: master
https://github.com/mongodb/mongo/commit/7e114c6dc901142c721a9ca7c7adc17edd4868e4

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