[
https://issues.apache.org/jira/browse/IGNITE-18856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764150#comment-17764150
]
Vladislav Pyatkov commented on IGNITE-18856:
--------------------------------------------
LGTM
> Switch primary replica calls from Raft leader to primary replica
> ----------------------------------------------------------------
>
> Key: IGNITE-18856
> URL: https://issues.apache.org/jira/browse/IGNITE-18856
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Assignee: Alexander Lapin
> Priority: Major
> Labels: iep-101, ignite-3
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *Motivation*
> As for now, RW requests to primary replica (see calls of
> `ReplicaService#invoke` ) are sent to raft leader, for which the refresh
> leader operation is needed. In presence of placement driver which is
> responsible for assigning primary replicas, this is not needed, the request
> can be sent directly to primary replica node.
> Th information about primary replicas assigned by placement driver should be
> available on every node after IGNITE-18859 . This task is about switching
> primary replica calls and eliminating excessive code related to refreshing
> leader of raft group.
> *Definition of done*
> Requests to primary replica are made to those nodes that are assigned by
> placement driver, and no related Raft calls are made.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
