[SERVER-51066] Deduplicate retried idempotent commands in profiler test utility Created: 18/Sep/20 Updated: 06/Dec/22 Resolved: 21/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The jstests/libs/profiler.js library is providing some functions to check existence and number of occurrences of oplog entries. Since retried idempotent operations are generating duplicate entries (as happened in BF-18868), this should be taken into account when calling profilerHasNumMatchingEntriesOrThrow and profilerHasSingleMatchingEntryOrThrow that are otherwise failing. A possible solution would be adding two equivalent functions profilerHasSingleIdempotentMatchingEntr[y|ies]OrThrow deduplicating commands presenting the same fields (maybe it is enough to just check the tuple <namespace, command type, clusterTime>). |