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

opWriteConcernCounters should track limited set of writeConcern

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • v4.0
    • Repl 2019-02-11

      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.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: