...

By maintaining a separate committedVoterSet, the system ensures:

• Safety: Quorum checks and leader decisions are based on a membership configuration that is guaranteed to be replicated and agreed upon by a majority.

• Stability: The committed voter set changes only at commit points, avoiding transient or rolled-back configurations.

• Correctness under Reconfiguration: Both during joint consensus transitions and simple add/remove operations, the system preserves Raft’s safety guarantees.

Benefit

This mechanism strengthens the Raft membership model by:

• Both committed and uncommitted voters participate in quorum decisions and elections. However, uncommitted voters (those whose VotersRecord has been appended but not yet committed) carry a risk: if the leader crashes before the VotersRecord is committed, the voter change maybe lost due to log truncation, leading to potential configuration inconsistencies.

• Stability: When the committed and uncommitted voter sets differ, the cluster is in a joint consensus phase.
  Exposing this state allows management and orchestration systems to recognize that the controller quorum is undergoing a transitional reconfiguration, and to avoid assuming the new configuration is already stable.

• Debugging and Compliance Verification: During troubleshooting or post-incident audits, operators and tools must be able to differentiate between committed voters and uncommitted voters that have started replicating but are not yet officially part of the quorum.This distinction is critical for confirming whether a reconfiguration completed successfully and whether the cluster’s control plane reached a consistent

• Making committed membership explicit.

• Providing a consistent interface for tooling.

• Improving the overall transparency and debuggability of the cluster state.

Public Interfaces

Request Schema

...

Committed voter present in current voters/observers
If a committed voter is also present in the current voters or observers set, its ReplicaState is identical to the corresponding entry in those sets. This ensures that all runtime fields within ReplicaState are available and reflect the current replica state.

...

Above fields are only meaningful for active replicas(voter) in the quorum. For committed voters, they are not strictly required—the sentinel values simply indicate that the data is unavailable or not applicable.

High watermark is unknown when a new leader is elected 

• In such case, the empty set should be returned because we don't know the high watermark.
• Committed voters can be returned as non-empty when leader update the high watermark.

Compatibility, Deprecation, and Migration Plan

...