Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:

Assigned Teams:

Sharding NYC
Backport Requested:

v5.0
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Should collect latency information as a histogram with coarse grained buckets (0-10ms,11-100ms,101-1000ms, 1001-10000ms, 10001+ms)
Should track total number of invocations that complete
Should report these metrics in serverStatus to be consumed by FTDC.
Should report these metrics in currentOp if there is a resharding operation currently in progress.

https://github.com/mongodb/mongo/blob/9cf1509ad2664830d37a7a128d43752dcac8556a/src/mongo/db/s/resharding/resharding_oplog_applier.cpp#L132

depends on

SERVER-57742 Create a non-specialized version of the OperationLatencyHistogram class

Closed

duplicates

SERVER-64388 Track and Report New Recipient Latency Fields in ServerStatus

Closed

Assignee:: [DO NOT USE] Backlog - Sharding NYC
Reporter:: Lamont Nelson
Participants:: [DO NOT USE] Backlog - Sharding NYC, Lamont Nelson
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jun 14 2021 08:12:08 PM UTC
Updated:: Dec 06 2022 01:13:55 AM UTC
Resolved:: Jun 09 2022 01:10:40 PM UTC