[
https://issues.apache.org/jira/browse/IGNITE-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-16012:
------------------------------------
Description:
We need to update the current {{changePeers}} behavior with the following:
- it must be asynchronous and returns ASAP when the request processed (without
waiting for data catchup)
- it must be updated with {{term}} argument for skipping the updates from old
terms
(Phase 1)
was:
We need to update the current {{changePeers}} behavior with the following:
- it must be asynchronous and returns ASAP when the request processed (without
waiting for data catchup)
- it must be updated with {{term}} argument for skipping the updates from old
terms
- when {{changePeers(term, peers)}} received:
-- it should be skipped with a special response {{Done}} if current peers is
the same
-- if {{term}} is not the same, we must reply with WrongTerm response
-- it must update catching-up peers, if the current node stage is
STAGE_CATCHING_UP and response with {{Received}}
-- if no active {{changePeers}} exists, start it and returns {{Received}}
-- it must respond {{Busy}} if the current stage of the node configuration is
not {{STAGE_CATCHING_UP}} or {{STAGE_NONE}}
(Phase 1)
> Raft changePeers behavior must be updated to async version
> ----------------------------------------------------------
>
> Key: IGNITE-16012
> URL: https://issues.apache.org/jira/browse/IGNITE-16012
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> We need to update the current {{changePeers}} behavior with the following:
> - it must be asynchronous and returns ASAP when the request processed
> (without waiting for data catchup)
> - it must be updated with {{term}} argument for skipping the updates from
> old terms
>
> (Phase 1)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
