[DOCS-13358] Investigate changes in SERVER-43832: Expose readConcern and writeConcern defaults in serverStatus Created: 21/Jan/20  Updated: 13/Nov/23  Resolved: 28/May/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-43832 Expose readConcern and writeConcern d... Closed
Duplicate
Participants:
Days since reply: 3 years, 36 weeks, 6 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This ticket added a new serverStatus output field - "defaultRWConcern" - that is included by default. This field is a BSON object that may contain the following fields:

  • defaultReadConcern -> Optional field representing the default read concern set by an administrator through the setDefaultRWConcern command. Present if a default is currently set.
  • defaultWriteConcern - Optional field representing the default write concern set by an administrator through the setDefaultRWConcern command. Present if a default is currently set.
  • epoch -> The epoch (unique generation id) of when the default read or write concern was last set. Present if a default has ever been set.
  • setTime -> The wall clock time when the default read or write concern was last set by an administrator. Present if a default has ever been set.
  • localSetTime -> The wall clock time when this node updated its understanding of the default read or write concern. Always present, even if a default has never been set.

Notably when FTDC calls serverStatus every second, this section is disabled. FTDC instead calls getDefaultRWConcern on every file rotation to collect the defaults.

Description of Linked Ticket

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" , }

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 28/May/20 ]

Completed as part of DOCSP-7544. See this commit

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