[SERVER-85757] Retryable timeseries update increases opcounters too much Created: 25/Jan/24  Updated: 06/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Frederic Vitzikam Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

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.



 Comments   
Comment by Steven Vannelli [ 30/Jan/24 ]

We should confirm whether this impacts serverless billing.

Generated at Thu Feb 08 06:58:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.