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

Retryable timeseries update increases opcounters too much

XMLWordPrintableJSON

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

      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:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            frederic.vitzikam@mongodb.com Frederic Vitzikam
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: