[IGNITE-19684] С++: Thin 3.0: Tx partition awareness

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: C++ ignite-3
• Epic Link: Client tx partition awareness
• Assignee: Igor Sapego
• Reporter: Pavel Tupitsyn
• Created: 08/Jun/23 08:01
• Updated: 04/Sep/24 16:10

Description

Currently, client sends a separate TX_BEGIN request when the user invokes transactions.begin_async() API:

• Extra network request.
• Chosen tx coordinator (server node that handles TX_BEGIN request) is random and in most cases won't be the primary node for enlisted keys.

Solution:

• On the client, do not send TX_BEGIN request when the user invokes transactions.begin_async(). Instead, start the tx "on demand" when it is first used in some API.
• Send two requests at once to the same node where the first enlisted operation goes (according to partition awareness, if applicable).

Issue Links

• is a clone of: IGNITE-19681 Thin 3.0: Tx partition awareness
• is related to: IGNITE-19399 ODBC 3.0: Support transactions