[IGNITE-22542] Synchronous message handling on local node

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Done
• Labels: ignite-3 ignite3_performance
• Epic Link: AI3 Performance
• Assignee: Kirill Tkalenko
• Reporter: Ivan Bessonov
• Created: 20/Jun/24 07:44
• Updated: 01/Jul/24 08:40
• Resolved: 29/Jun/24 06:29

Description

org.apache.ignite.internal.network.DefaultMessagingService#isSelf - if we detect that we send a message to the local node, we handle it immediately in the same thread, which could be very bad for throughput of the system.

"send"/"invoke" themselves appear to be slow as well, we should benchmark them. We should remove instantiation of InetSocketAddress for sure, if it's possible, it takes time to resolve it. Maybe we should create it unresolved or just cache it like in Ignite 2.

Issue Links

• causes: IGNITE-22560 Processing messages to yourself in a thread pool
• causes: IGNITE-22558 Optimize sending to yourself in DefaultMessagingService
• causes: IGNITE-22603 Add InetSocketAddress caching for DefaultMessagingService
• causes: IGNITE-22614 Get rid of @Marshallable in package org.apache.ignite.internal.partition.replicator.network
• causes: IGNITE-22615 Get rid of @Marshallable in ReplicaRequest
• causes: IGNITE-22631 Get rid of @Marshallable in org.apache.ignite.internal.tx.message