[IGNITE-13496] Java thin: Use non-blocking socket IO

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 2.10
• Component/s: thin client
• Release Note: Java thin: async operations don't block user threads on write; IgniteClient uses one worker thread for all connections instead of a dedicated thread for every connection.
• Ignite Flags: Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 29/Sep/20 08:54
• Updated: 03/Dec/20 09:25
• Resolved: 02/Dec/20 16:40

Description

IGNITE-7623 introduces async APIs to the Java thin client. However, socket writes still cause user thread blocking and thus reduce scalability.

Investigate and prepare an IEP to use non-blocking IO.

This ticket does not affect user-facing APIs, only changes the way we do IO internally.

Issue Links

• blocks: IGNITE-13719 Thin client silently closes channel after inactivity
• causes: IGNITE-13804 Java thin: avoid buffer copies in synchronous operations
• relates to: IGNITE-13378 .NET: Thin Client: Use non-blocking socket IO
• relates to: IGNITE-7623 Thin client Java API - async API
• links to: GitHub Pull Request #8483
• mentioned in: Page Loading...