[IGNITE-14224] Extend logging of client failure handling.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.1
• Fix Version/s: 2.11
• Component/s: clients
• Release Note: Additional logging helps to find root cause in case of client node failure but server nodes can`t detect it.
• Ignite Flags: Release Notes Required
• Assignee: Evgeny Stanilovsky
• Reporter: Evgeny Stanilovsky
• Created: 24/Feb/21 06:20
• Updated: 24/Aug/21 12:47
• Resolved: 16/Mar/21 09:22

Description

1. "Finished serving remote node connection " but this message doesn't contain node id, it should be added (check org.apache.ignite.spi.discovery.tcp.ServerImpl.SocketReader#body).
2. When client worker is removed from clientMsgWorkers, org.apache.ignite.internal.util.IgniteUtils#closeQuiet(java.lang.AutoCloseable) is used to close the socket, we don't see any exception if it has happened, closeQuiet should be replaced with org.apache.ignite.internal.util.IgniteUtils#close(java.lang.AutoCloseable, org.apache.ignite.IgniteLogger) which works in the same way but prints exception.

Issue Links

• relates to: IGNITE-15367 Socket shutdown produce unnecessary output
• links to: GitHub Pull Request #8824