[
https://issues.apache.org/jira/browse/IGNITE-23010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Efremov updated IGNITE-23010:
-------------------------------------
Description:
*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.-
After IGNITE-23019 we have an opportunity to remove {{getLeader}} flag while
raft-client is starting, this is the main goal of this ticket.
*Motivation*
-The main idea is to speed up tests that doesn't require raft-nodes and it's
internal logic.-
Reasons for such flag removal:
# Performance reason: replication gropus startup time reducing.
# Code simplification:
** less async chaining on CompletableFuture result;
** we shouldn't collect and then handling raft-clients starting futures on
replication groups stoppings.
*Definition of done*
# {{getLeader}} is removed.
# {{
was:
*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.
> 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.-
> After IGNITE-23019 we have an opportunity to remove {{getLeader}} flag while
> raft-client is starting, this is the main goal of this ticket.
> *Motivation*
> -The main idea is to speed up tests that doesn't require raft-nodes and it's
> internal logic.-
> Reasons for such flag removal:
> # Performance reason: replication gropus startup time reducing.
> # Code simplification:
> ** less async chaining on CompletableFuture result;
> ** we shouldn't collect and then handling raft-clients starting futures on
> replication groups stoppings.
> *Definition of done*
> # {{getLeader}} is removed.
> # {{
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
