[SERVER-39194] opWriteConcernCounters should track limited set of writeConcern Created: 25/Jan/19  Updated: 29/Jan/19  Resolved: 29/Jan/19

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backport Requested:
v4.0
Sprint: Repl 2019-02-11
Participants:

 Description   

To avoid the need for a mutex in ServerWriteConcernMetrics, we will remove the arbitrary maps. The opWriteConcernCounters will be reduced to: 

opWriteConcernCounters: {
    insert: {
        wmajority: <num>,
        wnum: {
            "0": <num>,    // only generate these fields if they are used
            "2": <num>,
            "3": <num>     // only include wnum up to 3
        },
        none: <num>
    },
    update: {
        wmajority: <num>,
        wnum: {
            "0": <num>,    // only generate these fields if they are used
            "2": <num>,
            "3": <num>     // only include wnum up to 3
        },
        none: <num>
    },
    delete: {
        wmajority: <num>,
        wnum: {
            "0": <num>,    // only generate these fields if they are used
            "2": <num>,
            "3": <num>     // only include wnum up to 3
        },
        none: <num>
    }
}

Note that the wtags section is removed, and we only include wnum up to 3. This can be extended back to the full syntax described in SERVER-38998 later on.



 Comments   
Comment by Tess Avitabile (Inactive) [ 29/Jan/19 ]

Closing in favor of SERVER-39267.

Generated at Thu Feb 08 04:51:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.