[
https://issues.apache.org/jira/browse/IGNITE-19477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev resolved IGNITE-19477.
----------------------------------
Resolution: Won't Fix
This task was created as a temporary solution for the release {{9.0.0-ea1}},
but seems that setting {{fsync}} to false resolved original problem.
> 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.
> *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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
