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

[jira] [Updated] (IGNITE-22837) Invocation of the local raft client happens in a different pool

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

Vladislav Pyatkov updated IGNITE-22837:
---------------------------------------
    Description: 
h3. Motivation
By our architecture, we are involving RAFT client from the same node where the RAFT node is. In this case, we do not need to change threads (the only case where we have it is an invocation in the network thread).
{noformat}
resolvePeer:org.apache.ignite.internal.benchmark.InsertBenchmark.kvInsert-jmh-worker-1 0.301 782499 782800
    Here is hidden 9.3 us
deserializedCommand:%node_3344%JRaft-Request-Processor-2 0.1 792100 792200
{noformat}
h3. Definition of done
Get rid of chnaging threads in loca RAFT node invocation. 
We already have the same logic for the replica manager (ReplicaManager#onReplicaMessageReceived).

  was:
h3. Motivation
By our architecture, we are involving RAFT client from the same node where the RAFT node is. In this case, we do not need to change threads (the only case where we have it is an invocation in the network thread).
{noformat}
onBeforeApplyCmd:%node_3344%JRaft-Request-Processor-3 0.2 5415400 5415600
    Here is hidden 6.1 us
RaftNodeOnEvent:%node_3344%JRaft-NodeImpl-Disruptor_stripe_2-0 0.0 5421700 5421700
{noformat}
h3. Definition of done
Get rid of chnaging threads in loca RAFT node invocation. 
We already have the same logic for the replica manager (ReplicaManager#onReplicaMessageReceived).


> Invocation of the local raft client happens in a different pool
> ---------------------------------------------------------------
>
>                 Key: IGNITE-22837
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22837
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> By our architecture, we are involving RAFT client from the same node where the RAFT node is. In this case, we do not need to change threads (the only case where we have it is an invocation in the network thread).
> {noformat}
> resolvePeer:org.apache.ignite.internal.benchmark.InsertBenchmark.kvInsert-jmh-worker-1 0.301 782499 782800
>     Here is hidden 9.3 us
> deserializedCommand:%node_3344%JRaft-Request-Processor-2 0.1 792100 792200
> {noformat}
> h3. Definition of done
> Get rid of chnaging threads in loca RAFT node invocation. 
> We already have the same logic for the replica manager (ReplicaManager#onReplicaMessageReceived).



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