[SERVER-46471] More detailed config commitment status in replSetGetConfig Created: 27/Feb/20  Updated: 06/Dec/22  Resolved: 02/Mar/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: safe-reconfig-related
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-44812 Expose the commitment of the current ... Closed
Assigned Teams:
Replication
Participants:

 Description   

In SERVER-44812 we added commitmentStatus as a field in the replSetGetConfig reply. If the user passes commitmentStatus: true in the request, then the reply will also contain commitmentStatus, which is true iff the current replica set config has satisfied both of the "config commitment" checks:

  1. The current config has propagated to majority of the nodes in the current config
  2. The last optime written in the previous config has been replicated by a majority of nodes in the current config

It could be useful to expose additional details. Specifically, we could add two more fields to replSetGetStatus, indicating whether condition 1 and/or condition 2 has been satisfied.


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