Skip to content

Conversation

@ivandika3
Copy link
Contributor

What changes were proposed in this pull request?

Please refer to https://issues.apache.org/jira/browse/RATIS-2382

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/RATIS-2382

How was this patch tested?

CI (https://github.com/ivandika3/ratis/actions/runs/20984539273)

| **Default** | false |


| **Property** | `raft.server.read.read-index.heartbeat.skip.enabled` |
Copy link
Contributor

@OneSizeFitsQuorum OneSizeFitsQuorum Jan 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for the idea and code.

Just want to discuss whether heartbeat.skip.enabled is a good name, I think maybe raft.server.read.read-index.leadership-check.skip.enabled

Copy link
Contributor Author

@ivandika3 ivandika3 Jan 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@OneSizeFitsQuorum Thanks for the review. I was also grappling with whether "leadership check" is a better name. However, my reasoning of choosing "heartbeat" is because we already have a LeaderStateImpl#checkLeadership to decide whether to leader need to step down due to lost majority heartbeats. LeaderStateImpl#checkLeadership does not send heartbeat, it simply checks the last RPC response time of the majority. Therefore, I picked "heartbeat" to explicitly mention the RPC that is going to be skipped.

That said, I'm ok if the community decide "leadership-check" is a more fitting name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants