[
https://issues.apache.org/jira/browse/IGNITE-16583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-16583:
-----------------------------------------
Description: Vault API is asynchronous but many of its usages include
calling {{join}} on the returned future immediately. We should remove as much
blocking calls as possible in order to avoid blocking critical threads. (was:
Current Vault API is asynchronous, which is inconvenient: underlying storage
implementations are synchronous and most of the API users immediately call
{{join}} on the returned futures.)
> Remove blocking calls on Vault methods
> --------------------------------------
>
> Key: IGNITE-16583
> URL: https://issues.apache.org/jira/browse/IGNITE-16583
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Minor
> Labels: ignite-3
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Vault API is asynchronous but many of its usages include calling {{join}} on
> the returned future immediately. We should remove as much blocking calls as
> possible in order to avoid blocking critical threads.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
