[SERVER-45438] Create serverStatus section for hedging metrics Created: 09/Jan/20  Updated: 29/Oct/23  Resolved: 22/Jan/20

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.3.3

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-13487 Investigate changes in SERVER-45438: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-27
Participants:

 Description   

Deliver a new serverstatus metric with the following subfields:

“hedgingMetrics”

  • numTotalOperations: NumberLong
    • A count of all operations with hedge options such that they could be hedged
  • numTotalHedgedOperations: NumberLong
    • A count of all operations that actually dispatched an additional rpc
  • numAdvantageouslyHedgedOperations
    • A count of all operations where a rpc other than the first one fulfilled the client request


 Comments   
Comment by Githook User [ 22/Jan/20 ]

Author:

{'username': 'cheahuychou', 'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com'}

Message: SERVER-45438 Create serverStatus section for hedging metrics
Branch: master
https://github.com/mongodb/mongo/commit/66ebefff6097f3122b121c73d034d1bcae5cf13e

Comment by Mira Carey [ 09/Jan/20 ]

At least for 4.4, the answer will always be '1'

So it wouldn't be a super informative field for this release

Comment by Bruce Lucas (Inactive) [ 09/Jan/20 ]

Would it be useful to also have a field that told us how many additional rpcs were dispatched?

Generated at Thu Feb 08 05:08:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.