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/02/19 11:41:00 UTC
[jira] [Commented] (IGNITE-17824) Use named executor instead of default one in order to process replica Response
[ https://issues.apache.org/jira/browse/IGNITE-17824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818455#comment-17818455 ]
Vladislav Pyatkov commented on IGNITE-17824:
--------------------------------------------
[~rpuch] This patch looks good to me.
Merged fef7aab39ef3262e1105af56c625ca5578a901d4
> Use named executor instead of default one in order to process replica Response
> ------------------------------------------------------------------------------
>
> Key: IGNITE-17824
> URL: https://issues.apache.org/jira/browse/IGNITE-17824
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3, storage-threading, threading
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Within ReplicaService.sendToReplica
> {code:java}
> private <R> CompletableFuture<R> sendToReplica(ClusterNode node, ReplicaRequest req) {
> CompletableFuture<R> res = new CompletableFuture<>();
> messagingService.invoke(node.address(), req, RPC_TIMEOUT).whenCompleteAsync((response, throwable) -> { {code}
> named executor should be used instead of default one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)