-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Expose each node's effective groupId and foundingOpTime in hello and replSetGetStatus responses. The reported value is the effective membership: on ASC the persisted (groupId, foundingOpTime) and on DSC the provider-derived groupId sentinel, which is always present.
Acceptance criteria
- hello and replSetGetStatus include the node's (groupId, foundingOpTime) when present.
- jstest asserting presence/absence across founding, clears, and initial sync adoption.
- Disagg jstest asserting reporting of the sentinel groupId
- depends on
-
SERVER-138106 Mint and announce the groupId at election (new-primary noop)
-
- Open
-
- is depended on by
-
SERVER-138127 Re-enable rid-sensitive dbHash checks in test fixtures with groupId-membership-aware opt-in
-
- Open
-
-
SERVER-138221 Found the groupId at setFCV upgrade completion
-
- Open
-
-
SERVER-138223 Clear the groupId on FCV downgrade (C2)
-
- Open
-
-
SERVER-138224 Clear the groupId on flag-off startup (C3)
-
- Open
-
-
SERVER-138239 FCBIS inherits the RecordIds groupId
-
- Open
-
-
SERVER-138309 Clear the groupId on standalone document-data writes (C4)
-
- Open
-