Retryable timeseries update increases opcounters too much

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I think I found another issue with timeseries metrics:

          metricChecker.checkMetricsWithRetries(
        "Update with retry and the shard key in the filter",
        [{update: 0, filter: {timestamp: key4}, updateMods: {$set: {x: 4}}}],
        {update: collName, updates: [{q: {timestamp: key4}, u: {$set: {x: 4}}}]},
        {updated: 1, updateCount: 1, updateShardField: "oneShard"},
        session.getSessionId(),
        NumberLong(13));

      This test increases serverStatus.opcounters.update by 2* the retry count with or without bulkWrite. A single document was matched.

      The test is bulk_write_metrics_single_shard.js.

              Assignee:
              Unassigned
              Reporter:
              Frederic Vitzikam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: