[IGNITE-19477] Custom operation timeout for sendWithRetry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Labels: ignite-3
• Assignee: Unassigned
• Reporter: Denis Chudov
• Created: 15/May/23 12:27
• Updated: 26/Jul/23 09:50
• Resolved: 26/Jul/23 09:50

Description

Motivation

Default operation timeout for sendWithRetry is 3000 ms and may be acceptable for such things as transactional requests. But for some other things, for example, DDL operations, it can be too small. When user creates a table, the least likely thing they expect is timeout exception after 3 sec. We should add argument with custom timeout for this operation.

Definition of done

sendWithRetry is able to be executed with custom timeout.

Implementation notes

In fact, we need raft commands to be executed with custom timeout, so an overloaded method should be added to RaftGroupService, and there is already sendWithRetry with custom timeout. 

Also, the timeouts for meta storage operations can be custimized at once.

Issue Links

• relates to: IGNITE-19275 Creation of big amount of tables throws exception