[
https://issues.apache.org/jira/browse/IGNITE-17814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17814:
-----------------------------------------
Fix Version/s: 3.0.0-beta2
> JRaft API should operate with Peers based on consistent ID
> -----------------------------------------------------------
>
> Key: IGNITE-17814
> URL: https://issues.apache.org/jira/browse/IGNITE-17814
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting a Raft service, a list of peers is required, which are
> identified by host-port pairs. However, Ignite nodes are identified by their
> consistent IDs, which requires an intermediate step of resolving consistent
> IDs into addresses. This is problematic, because a particular node may be
> offline and, therefore, impossible to resolve. It is proposed to use peers
> that are based on consistent IDs instead and move the handling of offline
> nodes into the Raft infrastructure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
