Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.1.0-rc0, 4.4.25, 7.0.2, 5.0.22, 6.0.11
Affects Version/s: 5.0.0
Component/s: Diagnostics
Labels:

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Backport Requested:

v7.0, v6.0, v5.0, v4.4
Sprint:
Repl 2021-11-01, Replication 2021-11-15, Replication 2021-11-29, Replication 2021-12-27, Replication 2022-01-10, Repl 2023-07-24
Case:
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Collecting the Feature Compatibility Version in FTDC would allow an easy anchor to what FCV is currently in use. Adding this as a metric would allow us to see the version change, or revert which can be an issue in some cases.

is duplicated by

SERVER-36140 Add featureCompatibilityVersion status to serverStatus response

Closed

SERVER-36826 Report setting of FCV in logs and diagnostics

Closed

is related to

SERVER-82087 FCVServerStatusMetrics::generateSection is racy

Closed

SERVER-62524 Represent FCV values meaningfully to remove dependency of utility functions on template file

Open

related to

SERVER-58533 Log FCV at initialization and on log rotation

Closed

SERVER-36140 Add featureCompatibilityVersion status to serverStatus response

Closed

(1 related to)

Assignee:: Sean Zimmerman

Reporter:: Kevin Arhelger

Participants:: Bruce Lucas, Diego Rodriguez, Eric Sedor, Githook User, Judah Schvimer, Kevin Arhelger, Samyukta Lanka, Sean Zimmerman, Vishnu Kaushik

Votes:: 1 Vote for this issue

Watchers:: 19 Start watching this issue

Created:: Jul 14 2021 04:49:58 PM UTC

Updated:: Apr 03 2024 02:05:04 PM UTC

Resolved:: Jul 21 2023 06:31:48 PM UTC

Confidence Status Last Update:: 11/Jul/23 2:49 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates