Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31246

Determine system.profile, top, opcount behavior with no-op retries

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding

    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

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: