[
https://issues.apache.org/jira/browse/RATIS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021867#comment-17021867
]
Lokesh Jain commented on RATIS-632:
-----------------------------------
[~szetszwo] Thanks for reviewing the patch. The cases where we will reject the
request are :-
# Maximum commit index - Majority commit index > configured limit1.
# Majority commit index - Minimum commit index > configured limit2
Maximum = max(commit index) for all peers
Minimum = min(commit index) for all peers
Majority = majority(commit index) for all peers i.e. for 3 node case it is the
2nd largest commit index.
The above limits also make sure that the Maximum commit index - Minimum commit
index < configured limit1 + configured limit2.
> Leader should throw ResourceUnavailableException when follower lags in commit
> index
> -----------------------------------------------------------------------------------
>
> Key: RATIS-632
> URL: https://issues.apache.org/jira/browse/RATIS-632
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Labels: ozone
> Attachments: RATIS-632.001.patch
>
>
> This Jira aims to determine pipeline slowness in leader using follower
> indexes (commit index and state machine last applied index). As part of Jira,
> configurations and algorithm would be defined for determining slowness.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
