Andrey Mashenkov created IGNITE-18325:
-----------------------------------------
Summary: Too many warning in logs when some grid nodes are
unavailable.
Key: IGNITE-18325
URL: https://issues.apache.org/jira/browse/IGNITE-18325
Project: Ignite
Issue Type: Bug
Reporter: Andrey Mashenkov
There are too many warning in logs when a node retry to connect to CMG node or
Metastorage node, which is unavailable.
Let's avoid printing stacktraces and print only meaningfull message with
throttling.
{code:java}
java.util.concurrent.CompletionException: java.net.ConnectException: Peer node1
is unavailable at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
at
java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1099)
at
java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
at
org.apache.ignite.internal.raft.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:493)
at
org.apache.ignite.internal.raft.RaftGroupServiceImpl.lambda$handleThrowable$27(RaftGroupServiceImpl.java:526)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
{code}
To reproduce run ItClusterStartupTest.
It may require a bit larger NODE_JOIN_WAIT_TIMEOUT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
