[SERVER-49971] Report current VectorClock time in serverStatus Created: 29/Jul/20  Updated: 29/Oct/23  Resolved: 23/Jun/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27
Participants:

 Description   

The sharding section in serverStatus currently reports lastSeenConfigServerOpTime (aka configOpTime). However, this field is being replaced by the VectorClock's ConfigTime component. Probably the current VectorClock time (currently ClusterTime, ConfigTime, and TopologyTime) should be reported somewhere in serverStatus. The clusterTime is currently not reported anywhere in serverStatus. We should choose an appropriate place to put these values, including appropriate interactions with FTDC. For example, since clusterTime (and to a lesser degree ConfigTime) increments frequently, it may not be efficient to fetch in a periodic collector in FTDC (but an onRotate collector should be okay). It should also be determined if this info should be ordinarily visible in serverStatus, or in a (possibly new) default-hidden section.



 Comments   
Comment by Githook User [ 23/Jun/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-49971 Report current VectorClock time in serverStatus
Branch: davish/SERVER-63099
https://github.com/mongodb/mongo/commit/8c5c658d24db081cfdb8e891c96edc052bd51c31

Comment by Githook User [ 23/Jun/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-49971 Report current VectorClock time in serverStatus
Branch: master
https://github.com/mongodb/mongo/commit/8c5c658d24db081cfdb8e891c96edc052bd51c31

Comment by Antonio Fuschetto [ 23/Jun/22 ]

Now the db.runCommand({serverStatus: 1}).sharding returns the following information:

{
  configsvrConnectionString: '__unknown_name__-configRS/ip-10-122-3-33:20002',
  lastSeenConfigServerOpTime: { ts: Timestamp({ t: 1655983422, i: 1 }), t: Long("-1") },
  lastSeenTopologyOpTime: { ts: Timestamp({ t: 1655983403, i: 1 }), t: Long("-1") },
  maxChunkSizeInBytes: Long("134217728")
}

Comment by Kaloian Manassiev [ 21/Oct/21 ]

Scheduling for WFBF day, but only to add config and topology optime. We should not add clustertime.

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