Vladislav Pyatkov created IGNITE-23076:
------------------------------------------
Summary: Start single timeout worker thread for several client in
one JVM
Key: IGNITE-23076
URL: https://issues.apache.org/jira/browse/IGNITE-23076
Project: Ignite
Issue Type: Improvement
Reporter: Vladislav Pyatkov
h3. Motivation
Currently, each client starts own timeout worker:
{code:java}
this.timeoutWorker = new TimeoutWorker(
log,
cfg.getAddress().getHostString() + cfg.getAddress().getPort(),
"TcpClientChannel-timeout-worker",
pendingReqs,
// Client-facing future will fail with a timeout, but internal
ClientRequestFuture will stay in the map -
// otherwise we'll fail with "protocol breakdown" error when a late
response arrives from the server.
false
);
new IgniteThread(timeoutWorker).start();
{code}
but in the case where we start several clients on one JVM, the only timeout
worker would be enough.
h3. Definition of done
All clients that were started in one JVM share the timeout worker.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
