[
https://issues.apache.org/jira/browse/IGNITE-26721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-26721:
-------------------------------------
Fix Version/s: 3.2
> Fix EBUSY state if raft snapshot has not been installed yet
> -----------------------------------------------------------
>
> Key: IGNITE-26721
> URL: https://issues.apache.org/jira/browse/IGNITE-26721
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> I discovered that if raft snapshot isn't set within
> *org.apache.ignite.internal.raft.configuration.RaftConfigurationSchema#responseTimeoutMillis*
> (the default is 3 seconds), it will trigger a second attempt to install raft
> snapshot, which will result in an error and the state being set to EBUSY.
> This needs to be fixed.
> The easiest way, at first glance, is to make the snapshot installation
> timeout sufficiently long, perhaps infinite, since we don't know how long it
> will take.
> Another option is to make raft snapshot set an idempotent operation and do
> nothing if the request comes back.
> Or perhaps a combination of these solutions, or something else entirely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
