You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2023/03/17 09:01:00 UTC

[jira] [Updated] (IGNITE-19051) Make topology aware client not dependable on Raft RPC server

     [ https://issues.apache.org/jira/browse/IGNITE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Chudov updated IGNITE-19051:
----------------------------------
    Description: After IGNITE-19014, topology aware raft client is closely tied with RaftManager and therefore, with IgniteRpcServer, containing message handler for leader change notifications. We should create separate component that would be able to contain this handler so that topology aware raft client would not require RPC server to start.

> Make topology aware client not dependable on Raft RPC server
> ------------------------------------------------------------
>
>                 Key: IGNITE-19051
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19051
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> After IGNITE-19014, topology aware raft client is closely tied with RaftManager and therefore, with IgniteRpcServer, containing message handler for leader change notifications. We should create separate component that would be able to contain this handler so that topology aware raft client would not require RPC server to start.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)