[IGNITE-18325] Too many warning in logs when some grid nodes are unavailable.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Grid start-stop scenarios
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 02/Dec/22 13:28
• Updated: 04/Sep/24 16:19

Description

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.

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)

Find reproducer in IGNITE-18171 PR in ignite-runner module org.apache.ignite.internal.cluster.ItClusterStartupTest tests
It may require a bit larger NODE_JOIN_WAIT_TIMEOUT.

Issue Links

• is caused by: IGNITE-18171 Descibe nodes start/stop scenarios