[
https://issues.apache.org/jira/browse/IGNITE-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701301#comment-17701301
]
Vladislav Pyatkov commented on IGNITE-19014:
--------------------------------------------
LGTM
> Topology aware Raft client creates its own message handler which is not aware
> of Raft group
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-19014
> URL: https://issues.apache.org/jira/browse/IGNITE-19014
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Chudov
> Assignee: Denis Chudov
> Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Topology aware client creates its own message handler for leader change
> notifications. These notifications does not contain group ids, which is a
> problem for adding such clients for partition replication groups. Moreover,
> having same message handlers for one type of messages in number that is equal
> to the count of topology aware clients seems not to be a good decision and
> leads to weird problems after adding topology aware clients for partition
> Raft groups, which appear as random integration tests fails.
> We should get rid of this handler in topology aware client and create
> dedicated message processor in RPC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
