[SERVER-31246] Determine system.profile, top, opcount behavior with no-op retries Created: 25/Sep/17  Updated: 27/Oct/23  Resolved: 06/Oct/17

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

No-op retries are recorded in system.profile, for the top command, and for opcounters, which causes jscore tests with no-op retries of retryable writes to fail, because the number of recorded commands is higher than the number sent explicitly by the test. It should be determined if these metrics should ignore retries, or if this is the desired behavior.

Failing retryable_writes_jscore_passthrough tests:

  • operation_latency_histogram.js
  • views_stats.js
  • top.js
  • profile2.js
  • profile3.js
  • profile_findandmodify.js

Generated at Thu Feb 08 04:26:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.