Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Sharding 2020-01-27
Description
Specifically, I'd like the following to be exposed in serverStatus (this is from the design document):
getDefaultRWConcern
|
defaults:
|
{ readConcern: \{ ... }, // empty obj if not set |
writeConcern: { ... } // empty obj if not set |
}
|
This is for metrics, to see how many people are using it once it launches.
My assumptions: If a user does not configure it, there will be no object. If a user does configure it, even to the default value, it will exist. (these are assumptions, not requirements, so if you envision something different let's talk)
Example:
user sets readConcern but not writeConcern:
defaultRWConcern:
{ readConcern: "local" , }Attachments
Issue Links
- is documented by
-
DOCS-13358 Investigate changes in SERVER-43832: Expose readConcern and writeConcern defaults in serverStatus
-
- Closed
-