You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2023/01/31 15:57:00 UTC
[jira] [Updated] (IGNITE-18682) Move Raft timeouts to Raft configuration
[ https://issues.apache.org/jira/browse/IGNITE-18682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Polovtcev updated IGNITE-18682:
-----------------------------------------
Description:
Default RaftManager implementation (aka Loza) contains multiple hardcoded timeout values:
# RETRY_TIMEOUT - timeout between network invocations
# RPC_TIMEOUT - timeout for waiting for a network response
# DELAY - delay between retry attempts
These values should be extracted into RaftConfiguration, so that they can be changed in tests, for example.
was:
Default RaftManager implementation (aka Loza) contains multiple hardcoded timeout values:
# # RETRY_TIMEOUT - timeout between network invocations
# RPC_TIMEOUT - timeout for waiting for a network response
# DELAY - delay between retry attempts
These values should be extracted into RaftConfiguration, so that they can be changed in tests, for example.
> Move Raft timeouts to Raft configuration
> ----------------------------------------
>
> Key: IGNITE-18682
> URL: https://issues.apache.org/jira/browse/IGNITE-18682
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Default RaftManager implementation (aka Loza) contains multiple hardcoded timeout values:
> # RETRY_TIMEOUT - timeout between network invocations
> # RPC_TIMEOUT - timeout for waiting for a network response
> # DELAY - delay between retry attempts
> These values should be extracted into RaftConfiguration, so that they can be changed in tests, for example.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)