[
https://issues.apache.org/jira/browse/IGNITE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789450#comment-17789450
]
Vladislav Pyatkov commented on IGNITE-20830:
--------------------------------------------
We have doubts about the implementation of a topology-aware RAFT client.
Currently, the subscription to the leader update occurs when the node appears
in the logical topology. So the questions are:
# Does a node have to appear in a physical topology when it appears in a
logical one?
# When a node leaves the cluster, is there only one way for a node to return to
the logical topology: return to the physical one and then appear in the logical
one?
> Do not retry attempts to subscribe in TopologyAwareRaftGroupService
> -------------------------------------------------------------------
>
> Key: IGNITE-20830
> URL: https://issues.apache.org/jira/browse/IGNITE-20830
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> h3. Motivation
> In IGNITE-20828, retries on UNsubscription were removed. It needs to be
> considered whether we should retry subscriptions or not.
> h3. Implementation notes
> * Replace the TopologyAwareRaftGroupService#sendWithRetry method with the
> simple netwotk invoke.
> * Move specific exception handling logic to the particular method
> (TopologyAwareRaftGroupService#unsubscribeLeader).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
