[SERVER-77797] Make analyze_shard_key.js concurrency workload only validate read and write distribution metrics if the sample population matches the mock query patterns Created: 05/Jun/23  Updated: 29/Oct/23  Resolved: 09/Jun/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc4

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
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
Operating System: ALL
Backport Requested:
v7.0
Sprint: Sharding NYC 2023-06-12
Participants:
Linked BF Score: 35

 Description   

As discovered in BF-28888, in suites with stepdown/kill/terminate or chunk migration, read and write queries are bound to get interrupted and retried; and when retries occur a lot, the actual query patterns would be very different from the intended query patterns and consequently the metrics would fall outside of the windows allowed by the metrics check. 



 Comments   
Comment by Githook User [ 12/Jun/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-77797 Make analyze_shard_key.js concurrency workload only validate read and write distribution metrics if the sample population matches the mock query patterns

(cherry picked from commit 771a07f38db24ddceb9ed4bd3306fead2fe74dc3)
Branch: v7.0
https://github.com/mongodb/mongo/commit/d6a819f64b9d6780f3877b884c5f81d759ea9fa0

Comment by Githook User [ 09/Jun/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-77797 Make analyze_shard_key.js concurrency workload only validate read and write distribution metrics if the sample population matches the mock query patterns
Branch: master
https://github.com/mongodb/mongo/commit/771a07f38db24ddceb9ed4bd3306fead2fe74dc3

Generated at Thu Feb 08 06:36:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.