[
https://issues.apache.org/jira/browse/IGNITE-19120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737513#comment-17737513
]
Vladislav Pyatkov commented on IGNITE-19120:
--------------------------------------------
[~maliev] [~Denis Chudov] Guys, please look at my PR.
> Raft client should get leader metadata along while getting leader itself
> ------------------------------------------------------------------------
>
> Key: IGNITE-19120
> URL: https://issues.apache.org/jira/browse/IGNITE-19120
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Motivation*
> This ticket is about TopologyAwareRaftGroupService which can subscribe on
> leader change. Necessary metadata is last log index and last applied index in
> leader's storage.
> This will allow to remove readIndex requests on acceptance of a lease on
> leaseholder candidate. As we know that no write commands in replication group
> can happen in absence of leaseholder, this means that leaseholder should just
> catch up leader's last log index received with leader metadata to make sure
> that its local storage is up-to-date. Applied index can be not reliable as
> leader may be being recovered and applied index maybe in progress of catch-up
> with log index, but it might be useful to know applied index on leaseholder
> candidate to justify time of waiting for actual storage state.
> *Definition of done*
> readIndex call is removed from Replica#waitForActualState.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
