[
https://issues.apache.org/jira/browse/IGNITE-19477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-19477:
----------------------------------
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.
was:TBD
> Custom operation timeout for sendWithRetry
> ------------------------------------------
>
> Key: IGNITE-19477
> URL: https://issues.apache.org/jira/browse/IGNITE-19477
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> *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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
