You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Efremov (Jira)" <ji...@apache.org> on 2024/10/08 16:51:00 UTC

[jira] [Updated] (IGNITE-23010) Remove getLeader flag from RaftGroupServiceImpl#start

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

Mikhail Efremov updated IGNITE-23010:
-------------------------------------
    Summary: Remove getLeader flag from RaftGroupServiceImpl#start  (was: Raft-client's starting parametrization with getLeader option)

> Remove getLeader flag from RaftGroupServiceImpl#start
> -----------------------------------------------------
>
>                 Key: IGNITE-23010
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23010
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mikhail Efremov
>            Assignee: Mikhail Efremov
>            Priority: Major
>              Labels: ignite-3
>
> *Description*
> After IGNITE-22373 and IGNITE-22691 several tests are passing longer because of there unintented (for tests cases) raft-nodes strating processes and related leader elections. This leads to ~10-15sec more duration per test. Even if we pass "getLeader" flag to \{{RaftGroupServiceImpl#start}} to \{{false}} state, it will negotiate the slowdown effect.
> *Motivation*
> The main idea is to speed up tests that doesn't require raft-nodes and it's internal logic.
> *Definition of done*
> # \{{getLeader}} is passed as \{{false}} from tests to \{{RaftGroupServiceImpl#start}} depends on test case.



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